Tag Info

Hot answers tagged

10

Sysprep allows you to do the following: Generates a new computer SID Set a new computer name Clear out event logs Run mini setup to deal with hardware differences Sysprep isn't necessary, as long as you change the SID and computer name. It's also a good idea if the hardware you're deploying to is the same or similar. There are tools that you can use ...


6

http://oem.microsoft.com/public/seo/sysprep.htm Microsoft does not provide support for computers that were set up with SID duplicating tools other than the Sysprep tool. I always sysprep using the recommended documented way, because it's recommended and documented. Picture this: you're having a bunch of issues with your PCs, you call PSS, you happen ...


6

It's kind of a weird design flaw in the Windows sysprep system. Joining the domain happens in the specialize phase. You can't be prompted to name the computer until the OOBE phase though. What I suspect is happening is that you are trying to name the computer in the out of box experience after you've already joined the computer to the domain. This breaks the ...


5

The language value is actually coded into each .wim file. it defaults with a new wim to en-US. You can use the dism tool in waik to set the language value on the wim image. Specifically the /Set-UILang switch. Check out the following documentation page for more information: http://technet.microsoft.com/en-us/library/dd744360(WS.10).aspx


5

Before you capture your WIM, configure your reference computer with whatever applications you want to have pre-installed. When the WIM is applied to a target, all that is left to do is join it to the domain and apply any updates. With that said, the beauty of using MDT (and by extension, SCCM) is that you can create separate application packages that can ...


5

If you have DNS and WDS running on the same box, a patch from over last summer (the DNS exploit patch) can cause this to happen. The fix for this is on Johan Arwidmark's blog. Hope that helps. Good luck.


5

Something I don't see people talking about is KMS in relation to sysprep. If you are planning on deploying a bunch of Windows 7 boxes, using KMS to license them, then you will have problems with the KMS server incrementing the count to activate. When you run sysprep you also create a unique CMID, in addition to the SID. The CMID is used with KMS to ...


5

This functionality has been added in Windows Server 2008 R2: Source from: http://www.deployvista.com/Default.aspx?tabid=36&EntryID=129 In Windows Server 2008 R2, Microsoft added support for using the PXE listener without Active Directory. Here is a complete guide on how to configure a standalone Windows Server 2008 R2 WDS Server ...


5

You can't (officially) install the snap-in on a non-WDS server, as far as I know (terrible, right?). You could always pre-stage the computer accounts so that you don't have to approve them. If that's the route you want to go, there's an excellent PowerShell script written by yours truly right here. :)


4

How can I deploy Windows 8 Pro over WDS so that it is already connected to my domain? After you read the documentation that I linked to in the comments, you should have an unattended file linked to your WDS install image. The <UnattendedJoin> section of that answer file is where you can input credentials that are used to join the client to the ...


4

Some of these components have excellent alternatives, some exist with limitations and some not at all. Integrating all this stuff to have a similar experience would be an enormous amount of work, and it would still be limited in various ways. Why would you want to do this?


4

I'm going to reply with a list of Linux alternatives for what's listed above.. DHCP on Linux WSUS is a tricky one to answer, did you want to keep Windows or other Linux machine up to date? Linux alternative to WDS (http://fogproject.org/) Linux file server (http://www.openfiler.com/) DNS server for Linux (http://www.isc.org/software/bind) Another DNS ...


4

I found all the different places that it needs to be updated but wanted to document them here incase anybody else ever runs into a similar issue. DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > General > Network (UNC) path DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > Rules > Edit ...


4

For ten laptops I would definitely use MDT. Download the package from Microsoft and read through the docs, they're quite good and cover all of the steps you need to make it go. If you encounter larger numbers of machines to deploy to I would then look towards WDS but use it with MDT. Microsoft Deployment Toolkit 2010 Microsoft Deployment Toolkit (MDT) ...


4

http://blogs.dirteam.com/blogs/sanderberkouwer/archive/2007/03/19/wds-without-active-directory.aspx First hit on google search for "wds without domain". Funny how admins today need serverfault to find people helping them to enter their question into google ;) To the topic: the answer is NO.


4

What is a boot image? A boot image is a slimmed down WinPE environment that is delivered to the client via PXE. It's similar to the first stage of the Ghost PXE install, where the client boots to a slim program before applying the image. It's what gets you started. What is an install image? This is the image that you capture (or the generic install.wim ...


3

In my opinion, always create an account for a specific job such as this. You will probably need to take into consideration as to where you've put your MDT Deployment Share. Some people tend to leave the Deployment Share on the boot drive of the WDS server or in some other easily accessible place in which the NTFS permissions aswell as Share permissions ...


3

I think your only option would be injecting the driver into the image using dsim.exe with the /forceunsigned switch.


3

You should look into using the Microsoft Deployment Toolkit (MDT). It can automate deployments of server and desktop operating systems. You can make it as automated as you like. Microsoft MDT


3

Run do not walk to the download site for MDT. You can set up task sequences based on any number of factors. You may need or want to set up a webservice front end to allow additonal capabilities in Ad or simply use the roles portion of the MDT database. This part of a pretty good tutorial talks about roles in the MDT database. I also would reccomend this ...


3

No it is not a requirement for Windows 7 to be PXE booted from a Windows 2008 server. Linux distributions can sometimes take time to "support" a new version, but in most cases all that needs to happen is that the bootloader files need to be added to the PXE server. Here is an example. http://www.ultimatedeployment.org/, ...


3

Have you configured DHCP options 66 and 67? 66 should be set to the WDS server and option 67 should be set to boot\x86\wdsnbp.com.


3

Have you tried using the NDIS5 Driver for Microsoft Windows driver? If you have trouble getting it into the VM, use something like genisoimage to generate an ISO you can mount in VirtualBox.


3

You need to add Option 66, and Option 67 (Boot Server and Boot Filename). Set the Boot IP to the IP address of the WDS server (if you specify a DNS server you can also use the hostname). Set the Boot Filename to boot\x86\wdsnbp.com A screenshot of our DHCP settings are below: See here for more information (look for Known issues with configuring Windows ...


3

I recently had this same issue and here's the basic steps of how to do it: Mount the WIM file like this: dism /Mount-Wim /WimFile:<x:\img.wim /Index:1 /MountDir:<x:\mountPath> Add the driver: dism /image:<x:\mountPath /Add-Driver:<x:\path\to\drivers> /Recurse Commit changes and unmount the WIM file: dism /unmount-wim ...


3

Under the "sources" folder on the PE key is the "boot.wim" file. Mount Boot WIM: dism /Mount-Wim /wimfile:C:[WPE PATH]\sources\boot.wim /index:1 /MountDir:C:\Mounted_images\boot Then the file can be found at: C:\Mounted_images\boot\Windows\System32\startnet.cmd Commit changes and Unmount WIM: dism /Unmount-Wim /MountDir:C:\Mounted_images\boot /commit If ...


3

Okay lets start with the sysprep.inf file. This is just a flat text file that doesn't interpret variables. The * is used to denote a random chosen computer name. The variables %MACHINENAME% and Others are replaced with the actual text string by WDS when it copies over the unattend file. So for any of this to work you have to be deploying it with WDS. The ...


3

The answer to 1 and 3 is "yes, but..." You may want to organize your drivers according to whether you need to use them in the boot (PE) images or the install images. Separating the drivers by model of computer can make it easier to replace the correct drivers when new versions are released. Updating the deployment share depends on where the drivers are going ...


3

I think you're trying to use individual retail or OEM licenses with WDS. Don't do this, get volume licenses so that you have KMS or a single Multiple Activation Key(MAK) available.


3

Generally, WDS is only used to deploy the boot image. It does not host the install image in a typical MDT deployment. With the correct hackery, you can deploy this boot image and unattend file through something like tftpd and pxelinux rather than WDS, but it's totally unsupported and also a nightmare to set up. You can always make a boot install CD instead ...



Only top voted, non community-wiki answers of a minimum length are eligible