I promised last week I would write a blog post on how I use OSDbackground in case of a Task sequence failure, so here it is. OSDbackground gives us the possibility to show an error in case a Task Sequence fails and when doing so it also provides us with the option to read all
I wrote a blog post a while ago on a tool my college Johan Schrewelius has published which sets the OSDbackground during OSD and gives us the possibility to troubelshoot without F8 support enabled which should be avoided. An update of OSDBackground is now published with som bug fixes like: 1. Added Management Point to
I have used Michael Niehaus excellent script for dumping all task sequence variables during OSD which is great for troubleshooting. https://blogs.technet.microsoft.com/mniehaus/2010/04/26/dumping-task-sequence-variables/ However it dumps all TS variables including: _SMSTSReserved variables which for instance contains the Network access account username and password in clear text. The same goes for the Domain Join account used in the
Great to wake up to a new release of Configuration Manager Technical Preview 1611! The Configuration Manager team must have been really busy, first shipping 1610 and then a week after 1611 technical Preview. Truly impressed by the work they are putting in the product! Not that many new features in 1611 Technical Preview though
There are many solutions out there for setting the OSD background to show progress during OS deployment. My college Johan Schrewelius at Onevinn has written a great one that shows: Time elapsed Host information Current OSD Step Custom background Yes, it works in full OS in Windows 8.1 and Windows 10 as well. Password Protected
I have gotten this question so many times now when writing scripts and blog posts what the difference is between a Task Sequence in MDT and SCCM. In some scenarios this makes a huge difference and is important to know about. When you execute an OSD Task Sequence in MDT you are logged on as
In Configuration Manager 1606 we got a new option to tweak our PXE boot times, TFTPWindowsSize which we can change in the registry on our PXE enabled DP’s. PXE booting a machine can never be fast enough! https://technet.microsoft.com/en-us/library/mt627944.aspx#BKMK_RamDiskTFTP Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPWindowSize Type: REG_DWORD The default value is 1 (1 data block fills the window)
Yesterday the Configuration Manager 1608 technical preview was released and just love the fact that we get a better end user experience in Software Center, I just had to write this. One of the new features in Software Center is that we can both see if there are new items and which item is new.