bobsapp

Thanks for the response. So it seems from what you're saying that it's really not possible using WDS. I guess I'll start to look into some sort of postinstall script that will do a nslookup and create a hostname changing script from that. Cheers

Hi folks, I just came onto the forum to ask a very similar question. I must say, I'm very surprised that this is how to set the hostname using WDS. I have my target client prestaged in ADS, I have a DHCP reservation for this client, and I have a static IP address in my DNS Server. Given all of these factors, I find it hard to believe that WDS must ystill prompt for the hostname (or create its own random name). Perhaps I have overlooked something? I have an old Windows 2003 RIS here, set up by someone else admittedly, and there the client hostname is presented on the first screen before continuing the installation. Simply put, is there no way using WDS to dynamically name the client according to the information from ADS / DNS / DHCP?

at long last I found the answer. So, for anyone else who needs to know how to copy files and folders across, as well as run a post installation script automatically, go here http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/e70bd077-cd4c-4fe7-875f-90ec5a26bee6

Hi - does anyone know how to set up a configuration set in Windows Deployment services for an unattended Windows 7 installation? I have searched and read and searched again and find the documentation to be frustratingly vague (as with all aspects of WDS it seems). Cheers

Hi MAVERICKS CHOICE, My 2 cents... I'm also interested in this as during my unattened installations I was ending up with 2 program files directoris. I understand the reason for the 2 different Program Files directories (32bit v 64bit), but I imagined that only NEW 32 bit applications would go into the "Program Files(x86)". I've just right now checked a *manually* installed Windows 7 installation (bog standard installation), and sure enough it has both directories with the same sub folders (Common Files, Internet Explorer, MSBuild, Reference Assembles....). So, my conclusion is that the files are needed by Windows and shouldn't be deleted (else why would it install them!) and secondly, it is not a phenomenon from an unattended installation. Cheers Bob

Thanks maxXPsoft, but surely this must be referenced in the unattended.xml somewhere, or?

Hi guys, Still no luck. I can install Windows 7 unattended, using WDS. All fine (eventually!). Now, I want to simply copy 2 directories containing files and folders during the unattended installation, from the WDS server to the client. No installation of these applications required, just copy. I have created a distribution share, and under $OEM$ Folders I have created sub folder c (meaning copy to C: drive), followed by opt and so on - so I want my files to be copied to c:\opt\... on the client. But now that this is created, how do I tell the unattend.xml to 'go and copy those files'? Unlike Out-of-Box Drivers, there is no right click context where you can specify "Insert to pass....". Anyone managed this? Cheers

Thanks for your response Johan. I'll take a look at MDT 2010 and see if this relieves my insanity somewhat :-)

Hi all, this is my first post in your forums. I am a UNIX guy who has been asked to set up Windows 2008 WDS to install XP, 2003, 20008 and Windows 7 clients, and I have to say, I have never seen anything so confusing and badly documented in my life. I have managed to get a basic unattended installation of Windows 7 64bit and am at the stage of now 'personalising' the installation. I thought I would start with what I thought would be an easy one: I would like to copy a bunch of files and packages from the WDS server to each Windows 7 client hard disk. No need to install them - simply copy them to the system and I'll install them later (they are bespoke applications). I believe there are multiple options for this - you can create a data .wim file and use this at some point to copy the packages across. However, as our packages are updated every 2 months or so, I thought it easier to use the 'older' method of a distribution share. This uses the $OEM$ folder structure, right? So, assuming my $OEM$ folder structure is correct (seems quite straightforward) and assuming I have chosen "Select Distribution Share" in Windows SIM, then how should I update my answer file to point to the share? How does the installation know that it should grab all these files and pace them in the appropriate location? Or, would you recommend I use a different option? (remember - this WDS server will continue to be used to roll out older Win2003 and XP clients - another reason to use the $OEM$ method?) Thanks so far folks, Bob