Search English (United States)  Svenska (Sverige)
Tuesday, February 07, 2012 ..:: Blog ::.. Register  Login
 Text/HTML Minimize

On March 21, the first day of MMS 2011, I announced the immediate availability of the Deployment Research blog and Deployment Research Facebook page. Sites filled with video-tutorials on how to deploy operating systems. Information about this new site, as well a bunch of other deployment related community sites was by the way also printed (thank you FedEx) and put in the attendee-bag (Thank you Microsoft) for every MMS 2011 attendee, about 4000 people.

This also means that the deployvista.com blog will not be much active anymore. It will still exist, but the content will gradually be migrated over to the new site, cleaned-up and converted into the new format…

Happy deployment, and I hope to see you online in the forums…

Regards / Johan Arwidmark
Microsoft MVP – Setup & Deployment


 Print   
 Blog_List Minimize

 Print   
 Blog_Archive Minimize

 Print   
 New_Blog Minimize
You must be logged in and have permission to create or edit a blog.

 Print   
 Solving Network timeout issues with OSD/ZTI Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 7/25/2007

If you have a routed, high latency or just a slow network, OSD (WinPE) might timeout when initializing the network... This is a workaround for the issue...

Background info
In the OSD FP Update Microsoft increased the number of network retries from five to seven in every component but the one actually needing it (osdshell.exe)   :)

Workaround, configure WinPE to start the network before launching osdshell...

1. Remove winpeshl.ini
2. Edit Startnet.cmd with the following info...

factory -winpe
osdshell
exit

Note: in really rare routed scenarios you might even need to add a timeout between "factory -winpe" and osdshell... I use the timeout.exe from Windows Server 2003 for this...

factory -winpe
timeout /t 5
osdshell
exit

Permalink |  Trackback

  
 Search_Blog Minimize

 Print   
Copyright Deployvista.com 2006-2010 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2012 by DotNetNuke Corporation