I instead try the option to open the meeting link in browser, and the page wants me to download and install the 'Lync Web App' (first step in the on-page instructions). I do so, and the go to the on-page step 2 which is 'connect to meeting'. That is supposed to open the Lync Web App in a new window to handle the meeting. This topic answers frequently asked questions about updating from Lync for Mac to Skype for Business on Mac. Skype Business For Mac Skype For Business Mac Client Skype for Business on Mac is the all new client that provides great communication experiences.
For Mac OSX systems, install the following updates before installing Office 365 components:
- Lync/Skype for Business for Mac 2011 update (configuration information is available here: http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh534388.aspx)
- Office for Mac 2011 Service Pack 3 (http://onlinehelp.microsoft.com/en-us/office365-enterprises/hh180727.aspx)
Configure Office for Mac to use your Office 365 credentials
To download Office for Mac from Office 365:
From the user portal, launch the Office 365 application.
Your Office 365 page opens to Outlook.
- Click the Settings icon in the upper right, and click Office 365 settings.
- In the Office 365 Settings page, click Software.
- In the Software page, click Office.
- Click Install to download the installer package for the latest version of Office for Mac.
To install Office for Mac 2011:
- Double-click the Office 365 installer file.
- In the Welcome screen, click Continue.
- In the Software License Agreement screen, review the license terms and click Continue.
- In the popup screen, click Agree to continue.
- In the Standard Install screen, click Install. (To change the installation folder, click Change Install Location.)
- If Safari is open, a popup screen appears that prompts you to close Safari before you can continue the installation. Click Close Application and Install to close Safari and continue the installation.
Download mozilla firefox for mac 10.8.5. When prompted, enter your Mac password and click Install Software.
The installer takes a few minutes to install the necessary files.
When the installer finishes, click Close.
The Microsoft Setup Assistant for Office 2011 opens.
- Click Sign in to an existing Office 365 subscription.
Enter your email address and click Next.
When prompted, enter your email address and password and click Sign in.
Your Office for Mac 2011 is installed and activated for use. Next, install the updates and then configure it for use with your Office 365 credentials.
To configure Outlook on Mac to use your Office 365 credentials:
- Open Outlook for Mac 2011.
- If you haven't already configured an account in Outlook, a screen displays prompting you to do so. Click Add Account, and then continue to the next step.
On the Tools menu, click Accounts.
- If this is the first account you're creating in Outlook for Mac 2011, under Add an Account, click Exchange Account.
- If you've previously created an email account for a different email address, in the lower-left corner of the Accounts dialog box, click + to add an account, and then click Exchange.
- On the Enter your Exchange account information page, in the E-mail address box, type your full user ID, for example,
Adele.Darwin@acme.com
. - In the Method box, make sure User Name and Password is selected.
- In the User name box, type your full user ID again.
- Type in the Password.
Make sure Configure automatically is selected, and then click Add Account.
After you click Add Account, Outlook performs an online search to find your email server settings.
In the dialog box that asks you if you want to allow the server to configure your settings, select the Always use my response for this server check box, and then click Allow.
After the new account is created you'll see the account in the left pane of the Accounts dialog box.
- Close the Accounts dialog box.
After the new account is created, you can view your mail by clicking the new account name in the navigation pane.
Configure Lync for Mac to use your Office 365 credentials
To download Lync for Mac from Office 365:
From the user portal, launch the Office 365 application.
Your Office 365 page opens to Outlook.
- Click the Settings icon in the upper right, and click Office 365 settings.
- In the Office 365 Settings page, click Software.
- In the Software page, click Lync.
- Click Install to download the main Lync installer package for the latest version of Office for Mac.
- In the Software page, click Lync for Mac 2011 update.
- In the Download center, click Download.
To install Lync for Mac:
- Double-click the Mac for Lync installer file to open it, and then double-click the Lync installer icon to start the installer.
- In the Welcome screen, click Continue.
- In the Software License Agreement screen, review the license terms and click Continue.
- In the popup screen, click Agree to continue.
- In the Standard Install screen, click Install. (To change the installation folder, click Change Install Location.)
- When prompted, enter your Mac password and click Install Software.
- When the installer finishes, click Close.
- Double-click the Mac for Lync Update installer file to open it, and then double-click the Lync installer icon to start the installer.
- In the Welcome screen, click Continue.
- In the Software License Agreement screen, review the license terms and click Continue.
- In the popup screen, click Agree to continue.
- In the Standard Install screen, click Install. (To change the installation folder, click Change Install Location.)
- When prompted, enter your Mac password and click Install Software.
- When the installer finishes, click Close.
To configure Lync on Mac to use your Office 365 credentials:
- Open Lync for Mac 2011.
- In the Lync for Mac sign-in window, type your user ID (joe.nguyen@acme.com) and password.
In the Lync for Mac sign-in window, click Sign In.
Lync opens and displays your Lync contacts.
Creates a new client version policy.Client version policies enable you to specify which versions of clients (such as Microsoft Office Communicator 2007 R2) will be able to log on to your Skype for Business Server system.This cmdlet was introduced in Lync Server 2010.
Syntax
Description
Client version policies represent a collection of client version rules; in turn, client version rules are used to determine which client applications are allowed to log on to Skype for Business Server.When a user attempts to log on to Skype for Business Server, his or her client application sends a SIP header to the server; this header includes detailed information about the application itself, including the software's major version, minor version, and build number.The version information included in the SIP header is then checked against a collection of client version rules to see if any rules apply to that particular application.If such a rule exists, Skype for Business Server will then take the action specified by the rule.For example, the rule might tell Skype for Business Server to allow the logon, to block it, or to allow the logon but then silently upgrade the client application to the latest version (for example, upgrade Communicator 2007 R2 to Skype for Business).
Client version policies, which can be applied at the global scope, the site scope, the service scope (Registrar service only), or the per-user scope, give you flexibility in determining which client applications can be used to access the system.For example, as a general rule you might want to prevent users from logging on to Skype for Business Server by using Communicator 2007 R2; you might want to do that because the older client application does not support the same features and capabilities as Skype for Business.However, due to hardware or software conflicts, you might also have a group of users who cannot upgrade to Skype for Business.In that case, you can create a separate rule -- and a separate client version policy -- that allows those users to log on from within Communicator 2007 R2.
Note, however, that anonymous users are only affected by global policies.That's because anonymous users are not associated with a site or service, and cannot be assigned a per-user policy.
New client version policies are created by using the New-CsClientVersionPolicy cmdlet.These new policies can be created at the site scope, the service scope (Registrar service only), or at the per-user scope.
It's important to note that client version policies do not apply to federated users; instead, federated users are bound by the client version policies used in their own organization.For example, suppose a federated user uses client A, a client allowed by the federated organization.As long as the federated organization allows the use of client A, this user will be able to communicate with your organization using that client.This will be true even if your client version policy blocks the use of client A.Client version policies enforced in your organization do not override the client version policies used in a federated organization.
Examples
-------------------------- EXAMPLE 1 --------------------------
In Example 1, a new client version policy is created for the Redmond site.Because no parameters are specified (other than the mandatory Identity parameter), the new policy will contain all of the default values for a client version policy.
-------------------------- EXAMPLE 2 --------------------------
The command shown in Example 2 creates a new client version policy for each site in the organization.To accomplish this task, the command first calls the Get-CsSite cmdlet without any additional parameters; that returns a collection of all the sites in the topology.This collection of sites is then piped to the Select-Object cmdlet, which extracts the Identity property for each site.Those Identities are then piped to the ForEach-Object cmdlet, which takes each site in the collection and creates a new client version policy for that site.
Parameters
Prompts you for confirmation before executing the command.
New Lync Client For Mac Download
Type: | SwitchParameter |
Aliases: | cf |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Enables you to provide explanatory text about the policy.For example, you might include information about the users that the policy should be assigned to.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Suppresses the display of any non-fatal error message that might occur when running the command.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Unique identifier for the policy to be created.To create a policy at the site scope, use syntax similar to this: -Identity 'site:Redmond'.
To create a policy at the service scope, use syntax similar to this: -Identity 'Registrar:atl-cs-001.litwareinc.com'.
The Registrar service is the only service that can host a client version policy. Dvd burning software for mac free.
Policies can also be created at the per-user scope.To create a per-user policy, use syntax similar to this: -Identity 'SalesDepartmentPolicy'.
Type: | XdsIdentity |
Position: | 2 |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Creates an object reference without actually committing the object as a permanent change.If you assign the output of this cmdlet called with this parameter to a variable, you can make changes to the properties of the object reference and then commit those changes by calling this cmdlet's matching Set-.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Collection of client version policy rules.You can add and remove rules from a policy by using the New-CsClientVersionPolicyRule cmdlet and the Remove-CsClientVersionPolicyRule cmdlet.To add a rule at the time you create the new policy, create the rule and store the value in a variable (for example, $x).You can then use syntax similar to this when creating the new policy:
New-CsClientVersionPolicy -Identity 'RedmondClientVersionPolicy' -Rules @{Add=$x}
Type: | PSListModifier |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
Globally unique identifier (GUID) of the Skype for Business Online tenant account for whom the new client version policy is being created.For example:
-Tenant '38aad667-af54-4397-aaa7-e94c79ec2308'
You can return the tenant ID for each of your Skype for Business Online tenants by running this command:
Get-CsTenant | Select-Object DisplayName, TenantID
Type: | Guid |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Skype for Business Server 2015, Skype for Business Server 2019 |
Describes what would happen if you executed the command without actually executing the command.
Type: | SwitchParameter |
Aliases: | wi |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Applies to: | Lync Server 2010, Lync Server 2013, Skype for Business Server 2015, Skype for Business Server 2019 |
New Lync Client For Mac
Inputs
None.The Get-CsClientVersionPolicy cmdlet does not accept pipelined input.
Outputs
The New-CsClientVersionPolicy cmdlet creates new instances of the Microsoft.Rtc.Management.WritableConfig.Policy.ClientVersion.ClientVersionPolicy object.