Phoenix-IT

Yay! Thank you, and it was updated yesterday.

Thanks, but it's still grabbing my OS version and automatically grabbing the Windows 7 64 bit version. I guess I'm going to have to build an XP system for the sole purpose of downloading the correct version of Silverlight for my deployment. And THAT, is absolutely ridiculous.

Every option you could want is covered in their Administration Guide: http://forums.adobe.com/servlet/JiveServlet/downloadBody/3063-102-1-3598/flash_player_11_6_admin_guide.pdf Search for "Adobe Flash Extract" to learn how to pull out the MSI packages, etc. from their Administrator's download. Sign up and they'll usually give you a site license to use it in about 5 minutes.

Can someone point me to Microsoft's download of Silverlight for Systems Administrators? I've been searching like mad and can only seem to find it on 3rd party sites, which means it may not be the latest version. When I go to the website specified in the Silverlight Deployment Guide there is no link for administrators or an enterprise version. It checks my system, see's that it's installed, and then refuses to give me a download link. If I disable the plugin, it automatically starts the 64 bit download, when what I need is the 32 bit version for XP SP2 & 3. Makes me wonder what exactly is going on over there at MS, that finding something so basic has become so difficult. Thanks for your help...

Hi Ladies and Gents... I'm having a couple of little issues with WDS on Server 2008 R2 Standard. The WDS Server is not connected to our main network, nor is it connected to the internet. I've set it up specifically for imaging groups of computers for our Desktop Support team. It's connected to a single switch that the clients connect to with no routing or anything like that going on. It's setup with AD, DNS and DCHP, all of which were left to the default setting when I added those roles before adding the WDS role. Almost everything is working fine. I've created boot and capture images, added drivers when necessary and I'm able to capture and re-deploy operating systems as expected. However, I have noticed when I boot more than one machine at a time, while the boot.wim is being transmitted to the machines, two of them can have the same IP address. Most of the time they seem to boot normally, but I do occasionally get an error that the setup program encountered a network error. Is this normal? Second, how many clients need to be imaging at the same time before multicasting will show significant advantage over the normal deployment option? Our desktop guys will probably be imaging anywhere from 5 to 20 machines at a time through a 10/100 or gigabit switch. (Some of the obscure notebooks don't like the gigabit switch.) The reason I ask is because I haven't been able to get multicasting working. I did set it up by-the-book according to Microsoft's WDS getting started guide, but the clients don't ever see the the multicast once they've booted. The only option they show is the normal disk loading process. If multicasting won't make a significant difference when imaging 20 computers on a single switch then it's hardly worth being concerned about. Thanks Much!