In A LOT of cases, MDT fails to clean up properly after a Failed or even Successful Task Sequence. These leftover files are a nuisance, and can cause the following error (The task sequence has been suspended). Ive come accustomed to using the Diskpart tool to perform a “Clean” against “Disk 0” to ensure all… Read More »
Some basic registry settings to help with speeding up Windows shutdown in XP. =========== START OF SpeedUpShutdown.reg =================== Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Control Panel\Desktop] "HungAppTimeout"="1000" "WaitToKillAppTimeout"="1000" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control] "WaitToKillServiceTimeout"="1000" =========== END OF SpeedUpShutdown.reg ===================== Reference: http://www.computing.cc/windows-xp/how-to-speed-up-shutdown-on-windows-xp/
In some cases, naming computers, naming log files, etc having a ramdom value is helpful. I found a quick way to accomplish this using a VBS include line in the CS.ini. RamdomNumber = #Randomize: Replace((RND()*10),”.”,””) # Will produce a fairly short random number(ie. 7055475). This can now be used throughout your INI.
This tool will change the way troubleshooting and recovery is done in the field. These tools are essential and we have found our ways to performing these tasks. The one I’m excited about is the “Remote Connection” functionality. Check out the SpringBoard BLOG for more info: http://windowsteamblog.com/windows/b/springboard/archive/2011/03/23/a-peek-into-the-upcoming-dart-7-release.aspx
