How to re-enable Teams auto-update in Windows 365
In some Windows 365 Cloud PCs, the ability for the installed Teams client to automatically update has been affected along with the ability to check for updates. To rectify the problem, Teams Machine Wide Installer and the Teams client must be uninstalled, and then reinstalled. Reinstalling Teams can be a difficult task to accomplish if one doesn’t wish to disturb end users at work. Further complicating the matter is that the Teams client automatically installs only on user logon. To lower the complexity of fixing the problem while not impacting end users, we have written a Proactive Remediation package that takes end users into account. More information on Proactive Remediation Link to the Teams Fix - Proactive Remediation Package The detection script is checking to see if the Teams client is installed in the Users’ profile, which exists under c:\users\[user name]\appdata\local\Microsoft\Teams. If it is not found there, it will return non-compliant. The remediation script first checks to see if it has successfully run to completion before. If it has not, it then checks to see if a user is logged in and in an inactive state. If the user is logged in and active, the script exits, and Proactive Remediation will try again later. If the user is not logged in or active, the remediation process begins. The remediation script downloads the latest version of the Teams Machine Wide Installer MSI, uninstalls the Teams client, uninstalls the existing Machine Wide Installer installation, checks for a Registry Key than can cause issues with Teams client installations, then checks the user state again. If the user is not logged into their Cloud PC, the script will return compliant. Once the user logs back into their Cloud PC, the Machine Wide Installer will trigger the Teams client installation automatically. If the user is logged in but inactive, the remediation script creates a child PowerShell script, and XML file used to create a scheduled task, and registers the scheduled task that will initiate the Teams client installation when the user reconnects to their Cloud PC. All files are downloaded to C:\Windows\Temp. The amount of time that the scheduled task stays active is configurable in the Remediation script by modifying the $DateOffset variable. The child script checks for the existence of files it is supposed to remove, and this is done to ensure that the Teams client isn’t reinstalled every time the user connects. If the files exist, the script assumes it hasn’t successfully run before and launches the Teams client installer. Once the installation is complete, the script will attempt to delete the scheduled task. If the user doesn’t have administrative rights, it will not be able to remove the scheduled task and it will expire at its given time. The script will then remove the files used in this process. If the user does not reconnect to their Cloud PC by the time the scheduled task expires, the remediation script will run again and recreate the scheduled task. All the scripts in this solution generate their own logs to help admins troubleshoot issues. These logs are all written to C:\Windows\Temp. These logs are: Detection Script - Teams-MWI-detect.log Remediation Script - Teams-MWI-remediate.log Child Remediation Script - Teams-MWI-remediate-child.log The remediation script automates the whole process but if you want to manually fix this issue, you can do so by following these steps: On the Cloud PC, navigate to Settings > App > Apps and features. Search for Microsoft Teams. Uninstall Microsoft Teams and Teams Machine-Wide Installer. Download the latest version of Microsoft Teams from here. Open a command prompt and install the Teams client using the following command: msiexec.exe /I %Filepath to the downloaded Teams MSI% ALLUSERS=1 Restart the Cloud PC. The Teams client is now installed with automatic updates turned on.
How do I turn off read only mode in Powerpoint
Hi, I have been working on a PowerPoint presentation slideshow. I have been using the same PowerPoint for the last 7 years ie adding new slides each year. However, this year It's not letting me save my work and states can't save because it is in read only mode. I still have another 200 slides to add, but have had to redo my work for the last 3 days. Since it not saving my work. Please advise. I need to have this slideshow done by next week. BTW: I've tried following instructions via the internet etc.
Windows Server 2022 - KMS Activation yet?
I noticed Friday on my company's VLSC site that there are now MAK and KMS keys for WS2022. I have confirmed that I can now activate 2022 with a MAK key, volume license. However, I'm unable to activate it via our KMS server. I found the KMS key on our VLSC site: Windows Srv 2022 DataCtr/Std KMS XXXXX-XXXXX-XXXXX-XXXXX-KQDWV KMS (Masked for privacy) I used these commands on our KMS server (running WS2016): slmgr.vbs /ipk KMS key slmgr.vbs /ato Both commands were successful. When I type slmgr.vbs /dlv all, I see this entry: Name: Windows(R), ServerDatacenter edition Description: Windows(R) Operating System, VOLUME_KMS_WS22 channel Activation ID: --- Application ID: --- Extended PID: 03612-04573-000-204477-03-1033-14393.0000-1972021 Product Key Channel: Volume:CSVLK Installation ID: --- Use License URL: https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail Validation URL: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx Partial Product Key: KQDWV License Status: Licensed Remaining Windows rearm count: 1000 Remaining SKU rearm count: 1001 Trusted time: 7/19/2021 7:39:34 AM Key Management Service is enabled on this machine Current count: 50 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal (Items masked for privacy) This all appears normal. Does anyone know why WS2022 won't activate yet? This is what I get on my WS2022 systems: Something prevented us from communicating with our activation servers. Wait a few minutes and then try again. Error code: 0x87E10BC6 I can even enter this command on the 2022 system to manually tell it to use our KMS server (Yes, I joined the 2022 system to our AD domain) slmgr.vbs -skms ourkmsserver.domain.name That works, but when I try: slmgr.vbs /ato It gives essentially the same error. Does anyone know if these keys are simply too new? Might there be a patch or MCU required on older Windows Server O/Ss to be able to activate newer versions? I know there was a patch back in the day that 2012 R2 KMS servers needed to install before they could successfully activate 2016 servers. Thank you for any info you may have! - Michael
Cannot Change Adapter settings
Windows Server 2019 TP build 17713 and earlier build 17650. I cannot change the network adapter settings when the server is a domain controller and logged in as a Domain Administrator. The following error will show up: Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item. I am able to change the network adapter settings on standalone server Windows 2019 TP logged in as local Administrator. Any tips to be able to change the network settings?OAuth 2.0 and third-party application ID: Timeline extended to June 30, 2022!
New implementation timeline: June 30, 2022 To provide our customers with best-in-class security across our services, Microsoft is implementing the use of Microsoft Identity Platform 2.0 (an evolution of the Azure Active Directory identity service) which uses the OAuth 2.0 authorization protocol. OAuth 2.0 is a method through which a third-party app can access web-hosted resources on behalf of a user, through a third-party application ID. This change only impacts Skype for Business IP Phones certified under 3PIP program. Deployment Type Impact Statement Skype for Business Online All phones must be updated and tenant admins must have approved phone partners App ID using the consent URL Skype for Business On-Premises Hybrid (With Modern Auth Deployed) All phones must be updated and tenant admins must have approved phone partners App ID using the consent URL Skype for Business On-Premises Hybrid (No Modern Auth) No Impact Skype for Business On-Premises No Hybrid No Impact As result of this change, Skype for Business IP Phone partners have made a code change to embed the partner specific application ID in their firmware. The customer tenant admin will be required to confirm consent to allow the third-party phone application to be granted the necessary permissions (the same permissions currently being used by Skype for Business IP Phones). Skype for Business IP Phone partners will provide customers with a partner specific consent URL. Customer admin will need to perform a one time, tenant wide (all users), consent per IP Phone partner (i.e. one consent URL for Yealink, one consent URL for Crestron, etc.) Microsoft IP Phone partners will post additional information via their own communication channels, including the firmware version that includes the necessary changes. This change requires customers to perform a 2 step process: Step 1: Accept permissions request using the consent URL (can be done at any time) Step 2: Upgrade all impacted phones to the firmware version communicated by the Microsoft IP Phone partners All certified Skype for Business IP phones must be updated by July 15th, 2020 (originally January 15th, 2020). Without the update, successful authentication to Microsoft services on IP Phones will fail. Specifically, signing to the device via web or using a user name/password on the phone will fail. Customers are encouraged to work with their certified Skype for Business IP Phone provider to make the update before the deadline.
Windows Server 2019 version info
Preliminary tests have revealed that the version of 'kernel32.dll' found on our current preview build Windows Server 2019 system is of the form '10.0.x.x'. Hence, it would appear that the major/minor version numbers have not changed, at least not as of yet, from those for Windows Server 2016. Checking the version of 'kernel32.dll' is the method suggested within the Microsoft docs that we use in order to determine the OS version. Will the version numbers be updated when goes production? If so, can you tell us what those version numbers will be ? Thanks, RobMicrosoft Teams Secondary Ringer is now generally available on Windows 365
We are happy to announce that Microsoft Teams Secondary Ringer is rolling out this week to the public on Windows 365. Secondary Ringer is a voice calling feature that allows Teams to signal an inbound call on multiple devices. Previously, only one sound output device was used to notify users of an incoming Teams call. For example, if the default device was a headset, the user may miss incoming calls when not wearing it. Secondary ringer allows Teams to signal the arrival of an inbound call on two devices, which means you can have two sound output devices of your choice to ring (e.g., your PC and headphones) when there is an incoming Teams call. Setting a Secondary Ringer To set a secondary ringer, go to the “Devices” section of Teams settings and select a device from the “Secondary Ringer” drop-down list. Secondary ringer will not work: If you are not connected to more than one suitable device, you cannot set a secondary ringer. If a device is not online (like a Bluetooth headset that is powered off), it cannot be used either. If you remove your PC from a situation where the secondary ringer is unavailable (for example, unplug a laptop and move out of the range of the headset’s Bluetooth connection), Teams removes the secondary ringer, and you’ll have to reconfigure it after you reconnect. Getting Started To use Microsoft Teams Secondary Ringer, the minimum Windows Desktop Client version 1.2.3004 is required to enable the feature on Windows 365. Set up Teams on Windows 365 Microsoft Teams comes included in the Windows 11/10 images optimized for Microsoft 365 apps. For more information on how to enjoy the best Teams experience, refer to the Teams on Cloud PC documentation.
Scheduled Task Windows Server 2019 (EDIT)
Hello guys, I'm having a problem with the Windows Server 2019 Task Scheduler. It does not work as in Windows Server 2012. What do I need to do to make this work? EDIT: Guys, what I figured out is that the task scheduler works for 1 simple task, for a given time. But it does not work to repeat every day, every 5 minutes, indefinitely. What has changed in Windows Server 2019?
