A great user policy that purges old user profiles from devices on reboot. Staggering the setting at 180 on week one, then 90 on week two and finally 30 days in the third week.
This setting can be found under Computer Configuration \ Policies \ Administrative Templates \ System \ User Profiles
After updating Configuration Manager 2012 R2 and adding the Windows 10 ADK, task sequences will no longer pre-provision BitLocker
With WinPE 10 it uses the AES-CBC 128-bit encryption method.
Add the following Run Command Line steps after Format and Partition and before Pre-provision BitLocker.
- Set EncryptionMethodWithXtsFdv – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsFdv /d 3 /f
- Set EncryptionMethodWithXtsOs – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsOs /d 3 /f
- Set EncryptionMethodWithXtsRdv – reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /t REG_DWORD /v EncryptionMethodWithXtsRdv /d 3 /f
Available Encryption Methods in WinPE 10
- Value Data: 3 (Description: AES-CBC 128-bit)
- Value Data: 4 (Description: AES-CBC 256-bit)
- Value Data: 6 (Description: XTS-AES 128 bit)
- Value Data: 7 (Description: XTS-AES 256-bit)
During a OSD task sequence in Configuration Manager, we ran into an error with a VBS script that has worked previously.
The error in the SMSTS.LOG file was: CScript Error: Can’t find script engine “VBScript” for script
The problem appears to be caused by a changed registry value: HKEY_LOCAL_MACHINE\Software\Microsoft\COM3\REGDBVersion
After some searching on the internet the solution was to add the modify the REGDBVersion to a value of hex:01,00,00
Add to task sequence via a Command Line: REG ADD HKLM\Software\Microsoft\COM3 /v REGDBVersion /t REG_BINARY /d 010000 /f
Had an issue with MDT failing to install Windows 10 via WSUS. I kept getting the 0x8024401C error.
I upgraded my WSUS on the Windows Server 2012R2 to version 4.0. Then upgraded the host to Windows Server 2016. Still receiving the same error.
After some more googling and trial and error I made the following changes to the IIS server for the WSUS Application Pool:
- Queue Length: From 10000 to 25000
- Limit Interval (minutes): From 5 to 15
- “Service Unavailable” Response: From HttpLevel to TcpLevel
- Private Memory Limit (KB): From 18342456 to 0
Build is now receiving updates from the WSUS server.
Due to the issues with the Windows 10 1607 build and WSUS updates, I have added the April 2017 Cumulative update into my Windows 10 image (install.wim).
Here are the steps that I completed:
Dism /Mount-Image /ImageFile:"C:\Servicing\Images\install.wim" /Index:1 /MountDir:C:\Servicing\mount\Windows
Dism /Add-Package /Servicing/Image:C:\Servicing\mount\Windows /PackagePath:C:\Servicing\MSU\windows10.0-kb4016635-x64_2b1b48aa6ec51c019187f15059b768b1638a21ab.msu /LogPath C:\Servicing\AddPackage.log
Dism /Unmount-Image /MountDir:C:\Servicing\mount\Windows /Commit
Once completed the Windows 10 WIM image will have the latest cumulative update installed.
Some light reading for the bus ride home:
Dell devices with TPM at the 2.0 level will not build on legacy BIOS systems.
A solution around this is to downgrade the TPM to 1.2 level.
This can be done using the Dell provided TPM firmware update utility.
Have a look here for the details: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11850.how-to-change-tpm-modes-1-2-2-0
Microsoft Premier Workshop – EMS + S Technical Workshop
The four-day EMS + S Technical Workshop for Spark will provide members of the Spark technical support and delivery team the skills required to understand and successfully configure and support Spark’s EMS customer solution.
The topics included within this Workshop include
- EMS Introduction
- Managing client access
- Defining and managing security & rights management
- Implementing & applying user templates
- Working with customer self-service options
In this Workshop, students will learn the tools used in EMS to help define and manage individual customer requirements within Sparks shared customer environment. This Workshop contains Level 300 content.
Key Features and Benefits
Each module is designed to provide participants with in-depth expertise, tools and experience in configuring and managing various EMS scenarios. As an exclusive Spark event students, will be able to deep dive on the Spark solution to define specific customer requirements. A series of User Scenarios will provide participants with the practical application of the features and functions they learn about.
This Workshop will include the following topics
- The Solution
- Connecting a customer
- Mobile device management
- Controlling conditional access – device and applications
- Managing compliance rules
- Applying exemptions
- Mobile application rules
Rights Management (RMS)
- Activating RMS
- Invoking and managing file protection
- Configuring templates
- Applying templates
- User experience
Azure Active Directory Premium (AADP)
- Identity and access management – Single Sign-On to access cloud apps from Windows, iOS and Android devices
- Data protection
- Self-service for employees – password and group management
- Password resets
- Group management
- Customized MyApps portal
- Integration with On-premises
User Scenarios – practical experience in applying the learning of the Workshop
Enable Hibernation: powercfg -h on
Enable Fast Startup: REG ADD “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power” /V HiberbootEnabled /T REG_dWORD /D 1 /F
Disable Hibernation: powercfg -h off
Disable Fast Startup: REG ADD “HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power” /V HiberbootEnabled /T REG_dWORD /D 0 /F
Microsoft Intune is setup and you are browsing through the Admin section. You notice the below message on a number of pages:
Microsoft Intune was not able to retrieve all the data
You save and review the log file. The second line reads:
Error occurred while retrieving JWT token, check that current user has an Intune license and try again.
You need to assign a Intune A Direct license through the Office365 Admin Center. Ensure you have appropriate Administrative permission in Office 365.