Introduction Microsoft just introduced an updated kit for IT pros to plan, test and validate deployment and management of desktops running Windows 10 Enterprise and Microsoft 365 Apps for enterprise. This was earlier known as “Windows insider lab for Enterprise” or “Olympia”. The lab will cover technologies: So
Last updated 14.08.2020 Introduction I have written the following blog to share some of the valuable sources of information I have discovered while developing my knowledge related to the rollout of Modern Workplace clients using Microsoft365 Intune and Autopilot. Instead of a standard how to guide I have decided
It is no secret that MDT 2013 Update 1 had more than one problem: MDT 2013 Update 1 Release Notes and Known Issues Microsoft has now updated MDT 2013 Update 1 to build 8298 and fixed some of the problem but as you can read here there are still known
Links: Part 1, Part 2, Part 3, Part 4 OSDAdapter0EnableWINS Set this to True to use WINS for name resolution. Task Sequence example: OSDAdapter0EnableWINS=True OSDAdapter0WINSServerList Comma-delimited list of WINS server IP addresses. This property is ignored unless EnableWINS is set to True. Result in Windows: Task Sequence example: OSDAdapter0WINSServerList=10.10.10.1,10.10.10.2 OSDAdapter0TcpipNetbiosOptions
Links: Part 1, Part 2, Part 3, Part 4 OSDAdapter0DNSServerList Comma-delimited list of DNS servers for the adapter. Result in Windows: Task Sequence example: OSDAdapter0DNSServerList=10.10.10.1,10.10.10.2 OSDAdapter0DNSDomain Domain Name System (DNS) domain for the adapter. Result in Windows: Task Sequence example: OSDAdapter0DNSDomain=gt.local OSDAdapter0EnableFullDNSRegistration Set to True to register the IP address
Links: Part 1, Part 2, Part 3, Part 4 OSDAdapter0EnableDHCP Set this to True to enable Dynamic Host Configuration Protocol (DHCP) for the adapter (obtain an IP address automatically). Setting it to False will disable DHCP (Use the following IP address). Result in Windows: Task Sequence example: OSDAdapter0EnableDHCP=False OSDAdapter0IPAddressList Comma-delimited
Links: Part 1, Part 2, Part 3, Part 4 This is the first post were I will take a closer look at the variables available to set network card settings in a task sequence. The variables are available both in MDT and in plain SCCM OSD, they can be set
When you have task sequences that uses MDT 2012 boot images they will no longer work after upgrading SCCM to 2012 R2. The boot image will boot as expected but the task sequence ends unexpectedly at Setup Windows and ConfigMgr. In the SMSTS.log you might see the error: Failed to
One way to set a environment system variable during a MDT or SCCM Task Sequence is to use the SETX command. http://technet.microsoft.com/en-us/library/cc755104(v=ws.10).aspx This command SETX LLVAR TEST /M will set the variable LLVAR to the value TEST If we take a closer look at the System variables after this step,
When deploying computers in a new setup, I need to set various settings as default settings for all new users. One way to do this in your MDT or SCCM task sequence is to load the Default User Hive make the changes and save it again. When a new user
Modern Workplace consultant and a Microsoft MVP in Windows and Devices.
Infrastructure architect with focus on Modern Workplace and Microsoft 365 security.
Cloud & security specialist with focus on Microsoft backend products and cloud technologies.
Cloud & Security Specialist, with a passion for all things Cybersecurity
Cloud and infrastructure security specialist with background in networking.
Infrastructure architect with focus on design, implementation, migration and consolidation.
Infrastructure consultant with focus on cloud solutions in Office365 and Azure.
Modern workplace and infrastructure architect with a focus on Microsoft 365 and security.
