- HOW TO DISABLE SKYPE FOR BUSINESS ON OFFICE 365 INSTALL
- HOW TO DISABLE SKYPE FOR BUSINESS ON OFFICE 365 UPDATE
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync To stop this one showing at first launch, set this key to ‘1’: Can be annoying, and you can just surpress it from running the first time too, but let people read it on demand instead. Next is the ‘Welcome – Skype for Business’ screen. HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General
There’s the ‘First things first’ screen which you most likely don’t want users to see:
I’ve also seen a few screen nags after deploying the client.
HOW TO DISABLE SKYPE FOR BUSINESS ON OFFICE 365 INSTALL
I’m not sure what reason you’d install Skype for Business 2016 standalone if you can just install that single component of Office 2016, but it’s a gotcha that might affect someone down the track. This is important, because if you install the standalone version then try to install Office 2016, it won’t like that Skype for Business is installed already, and tell you to uninstall before continuing.
A standalone Skype for Business 2016, and then as part of the Office 2016 suite, it’s one of the components (just like Word or Excel). In this case, a single messaging policy applies to guests is under Org-wide Settings, which is updateable.I’ve been mucking around with Skype for Business 2016 and wanted to document what I’ve found.įirst, there’s two seperate installs. Guests also create and send messages within Teams, so they have their own settings in TSBAC (Figure 4). Certainly, large tenants need some way to automate policy assignment.
HOW TO DISABLE SKYPE FOR BUSINESS ON OFFICE 365 UPDATE
This might come in a future version of the console, or Microsoft might update the PowerShell module for Teams to allow administrators to form collections of users (perhaps all those belonging to a department or country) and stamp those accounts with a Teams policy. I don’t see any evidence of bulk edit capability today where you can select sets of users and apply the same policy to that set. Using policies to control access to functionality assigned at user level is good – you don’t have to get down to that level of granularity and can use the Default policy, but it’s nice to have the ability to create and assign different policies to different user groups if needed. See Microsoft’s documentation for more information about the migration of settings to TSBAC.įigure 3: Assigning a Teams policy to a user (image credit: Tony Redmond) As settings move, their departure is highlighted in the Office 365 Admin Center (Figure 1). Over time, Microsoft is moving Teams configuration settings from the Office 365 Admin Center to the TSBAC. The New Way to Manage Teamsįrom a Teams perspective, the big new piece of functionality is the transition from per-tenant settings to policy-driven control over what users can and cannot do inside Teams. This is part of the transition of Teams to take over from Skype for Business Online. Microsoft will combine the features available in the current Skype for Business Online own console (lovingly referred to as the “legacy portal” here), and the settings that control how Teams behave and who has access to the application (now found in the Settings section of the Office 365 Admin Center) to deliver a single place to manage both Teams and Skype for Business Online. Microsoft needs that time to build out features and transition work from other places in Office 365.īut going forward, the direction is clear. In other words, give it a month or so to before you can expect to use this interface in any serious way. The TSBAC is a work in progress and lots of the functionality does not yet work, so this is very much a “ kick-the-tires and tell us what you think” kind of console. The new admin center is not yet listed in the 12 other admin centers accessible from the Office 365 Admin Center, but you can get to it at (see above). On April 4, Microsoft announced that they have begun the roll-out of a new Teams and Skype for Business Admin Center (TSBAC – my term, not Microsoft’s) to Office 365 tenants. The Joy of Yet Another Office 365 Console
0 kommentar(er)
