Iroqouiz

Ok. So 1 device is added to 2 collections. And it can only PXE boot to the first one?

I'm seeing that sometimes as well. This has helped me in the past

Edit: it's not clear, is the deployment required or available? Try right clicking the device (computer) and select "Clear Required PXE Deployments"

This can't be SCCM related. SCCM will never remove anything at all from the data source share. Check if there isn't some script/scheduled task/evil admin that's deleting the source files.

Can you upload the file somewhere instead, it's hard to read like that.

You shouldn't put a manual restart step after "Setup Windows and Config Mgr", it will restart automatically anyway.

Hi, We have a small office in Stockholm and remote offices in Singapore and London. We have maybe 300 users and max 500 workstations. There are Riverbed appliances to optimize WAN speed to both locations. Now we are in the process of setting up SCCM environments in S and L so we can PXE boot machines and deploy software quicker etc. I'm thinking about setting up remote DPs in both S and L, that seems like the best solution. Do you guys have any better suggestions? What should I do about boundaries and boundary/dp groups? Is there anything I should think about before going ahead with this? I will be travelling to S in a few weeks time and have about a week to get this and some other stuff done. Thanks.

Will it be supported to upgrade from SP1 or will I have to set up a new server?

If WDS is installed on a Server 2012 RTM, does that support UEFI network boot out of the box? And how can I make sure the TS supports UEFI? Thanks.

For the record, I did what Peter suggested, and that works like a charm. Only difference is that I added the WindowsSource property to my CustomSettings.ini instead of setting the variable in the TS directly.

Have you configured boundaries and boundary groups? Can you take a screenshot of those settings?

Which log?

Of course that's possible. When you create a TS you can choose if it will be used to capture an image. Check out the guides on this forum. http://www.windows-noob.com/forums/index.php?/topic/6353-using-system-center-2012-configuration-manager-part-7-build-and-capture-windows-7-x64-sp1/

Is the server's computer object placed in the local Administrators group on the server?

1. Yes, you can. 2. Yes, you should. PXE booting and pressing F12 depend on how you deploy (advertise) your TS. If you make it available to SCCM clients (ie Software Center) and not just PXE it would automatically reboot and start the TS. You wouldn't have to do anything. 3. If you don't set up USMT all files will be lost. USMT means that before formatting the drive, the TS will back up the files and place them on, for instance, a network share. When the computer has been imaged, the TS will then restore the files. The applications will not be restored. With MDT (Microsoft Deployment Toolkit) you can actually make the TS scan your existing applications before wiping the drive, and then automatically install those apps after imaging. I haven't tested this, but sounds pretty cool in theory. You should research how you want to do this. It's not something that's done in a day. When you've decided how to proceed, you'll want to test the TS thoroughly in a lab before going live.

A couple of thoughts, not sure if any of them will solve your problem. 1. Is this happening will all machines? Physical or virtual or both? SP1 boot images run WinPE 4. When I upgraded to SP1 my VMs bombed out when PXE booting (with a similar error message I believe) because my VMware Workstation version was older and didn't support booting machines into WinPE 4. 2. When I upgraded to SP1 my DP started behaving strangely also. I had always configured WDS manually, placing the RemoteInstall folder on a different drive than the DP. It had worked fine for me in the past. But now I couldn't PXE boot either (with a similar, but different I believe, error code as yours). I first unchecked "Enable PXE support for clients" on the properties of my DP. Then I uninstalled WDS, removed the RemoteInstall directory, rebooted the server. I now let SCCM install and configure WDS for me. It placed the RemoteInstall dir on my DP drive instead. Since then I haven't had any issues with PXE.

What do you mean? Don't you already have the product key on Microsoft's licensing site?

So is the client package distributed to the DPs? Have you clicked Update Distribution Point? What are the installation properties of the client package in your TS?

You should check the wsyncmgr.log file on your server. See if it lists any errors in the sync.

I've fiddled around with this also and have never found a way to set that property. This is a collection I created with that option set in the gui. But that is not reflected when I run the Get-CMDeviceCollection cmdlet

I believe it would be the network access account.

Hi, Been wondering some things about app simulation. I've googled this but couldn't find anything useful. What is the difference between Success and Simulate Success in this screenshot? cheers

And you are actually clicking "Update Distribution Points" after? It would probably take a long time to update the image on the DP, are you waiting long enough? When you update, also open the distmgr.log file on the server and see if you get any errors.

It's set to only download the Patch Tuesday updates, according to the guide on this forum. But hadn't noticed he creates a new update group every time. Will try that. Thank you. http://www.windows-noob.com/forums/index.php?/topic/6799-using-system-center-2012-configuration-manager-part-9-deploying-monthly-updates/

Anyone have an idea as to what to troubleshoot? Thanks.