There any procedure to migrate the WDS Windows 2003 to Windows 2008 without losing the installation images? thanks

Hi Thor Take a look at this http://araihan.wordpress.com/tag/ris-to-wds/ and this http://technet.microsoft.com/en-us/library/cc771670(WS.10).aspx#BKMK_155 Regards zizebra http://auction.joyoustimes.net

Hi, From the problem description, I understand that you would like to migrate the WDS from Windows Server 2003 to Windows Server 2008 without losing any images. As we know, Windows server 2003 supports both RiSetup and RiPrep images, as well as Wim files. Windows Server 2008/2008 R2 only supports Wim files. If you are using the wim files on your Windows Server 2003, you should be able to use those files without changing on Windows Server 2008 R2. The best way to do this is to export the images from the server back into standalone WIM files, and then import those images onto your new server. From the WDS management console, you can right click on an image and select "Export Image". This will allow you to save the image off to a directory somewhere. You can then directly import this image to the new server. Regards, JamesJames Xiong TechNet Community Support

Thre is no actual procedure to migrate the WDS server role. You simply copy the image (.wim) files to the new repository folder. I think the default folder name is RemoteInstall. You could upgrade your current server if there anre not any other server roles to complicate the procedure. WDS 2008r2 configuration: http://technet.microsoft.com/en-us/library/dd348502(WS.10).aspxMCTS - Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

For WDS queries, post here. http://social.technet.microsoft.com/Forums/en-us/winserversetup/threads Thanks

Marius is correct. You need to deploy a new WDS server on 2008 and then you can convert and import the old images as .WIMs on new WDS server image repository. You can use wdsutil for converting existing RIPrepImages to .WIMs. For more info on wdsutil, pls refer : http://technet.microsoft.com/en-us/library/cc771206(WS.10).aspx~Santosh

start reading from here http://thommck.wordpress.com/2010/05/06/how-to-migrate-windows-deployment-services-to-a-new-server/http://www.virmansec.com/blogs/skhairuddin

Like I said there is no complicated procedure to "migrating" the WDS role but If you would like to somehow be sure that the service remains intact you could create a full backup and restore it on another server(if you have the hardware resources available) or a virtual machine and then perform an upgrade from 2003/R2 to 2008/R2 and see if all goes ok. If its ok then you could perform this in your production enviroment, but again the simplest way is to stop the WDS service, move the image store, start the service on the new WDS. The following are known issues with WDS that you should be aware of before you do anything: Known issues with configuring Windows Deployment Services Internet Protocol version 6 (IPv6) is not supported for Windows Deployment Services in Windows Server 2008. Windows Server 2008 R2 does not support IPv6 for network booting, but does support IPv6 for deploying images. If you are running Windows Deployment Services and a non-Microsoft DHCP server on the same computer, in addition to configuring the server to not listen on port 67, you will need to use your DHCP tools to add Option 60 to your DHCP scopes. If DHCP is installed on a server that is located in a different subnet, you will need to do one of the following: (Recommended) Configure your router to forward broadcast packets. All DHCP broadcasts by client computers on UDP port 67 should be forwarded directly to both the DHCP server and the Windows Deployment Services server. Also, all traffic on UDP port 4011 from the client computers to the Windows Deployment Services server should be routed appropriately (these requests direct traffic, not broadcasts, to the server). Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com. For more information, see Managing Network Boot Programs (http://go.microsoft.com/fwlink/?LinkId=115304). If Windows Deployment Services and DHCP are running on the same computer, configuring Windows Deployment Services to not respond to any client computers will not work. This is because although Windows Deployment Services will not respond, DHCP will. You can try to work around this issue by disabling DHCP option 60 on the DHCP tab Hope it helps, Marius MCTS - Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, From the problem description, I understand that you would like to migrate the WDS from Windows Server 2003 to Windows Server 2008 without losing any images. As we know, Windows server 2003 supports both RiSetup and RiPrep images, as well as Wim files. Windows Server 2008/2008 R2 only supports Wim files. If you are using the wim files on your Windows Server 2003, you should be able to use those files without changing on Windows Server 2008 R2. The best way to do this is to export the images from the server back into standalone WIM files, and then import those images onto your new server. From the WDS management console, you can right click on an image and select "Export Image". This will allow you to save the image off to a directory somewhere. You can then directly import this image to the new server. Regards, JamesJames Xiong TechNet Community Support

Hi, Any Update? JamesJames Xiong TechNet Community Support