Jorgen Nilsson

Hi, Have the devices the Configuration Manager 2012 client installed on them? If so the heartbeat that the client sends will also re-register the client back again regardless of the discovery settings. If you check properties of the client you are able to see what discovery method added the client and when, that way you can verify that you delete was succesful and what process is adding it back. Regards, Jörgen

Hi, I have seen that as well in some scenarios where the sccm client is uninstalled for instance, that is why it is important to set the group policy to disable automatic updates, have you done that? Regards, Jörgen

Hi, I normally deploy IE11 with the patch using a wrapped installation instead of using Software Updates, one reason beeing that you want to prompt the user that IE is about to upgrade and the patch itself. I have used the PS App deployment toolkit a number of times. https://psappdeploytoolkit.codeplex.com/ Regards, Jörgen

Hi, I have only seen it in the scenario where you don't have permissions to all instances. http://ccmexec.com/2013/03/configmgr-2012-automatic-client-upgrade-grayed-out/ Have you verified that? Regards, Jörgen

Hi, Which server the clients get there IP address from is a network related topic, are the clients in different subnets? In server 2012 you could perhaps use DHCP policies to solve it but not in Server 2008 r2. Regards, Jörgen

Hi, Are you using Dynamic memory on the VM? is so don't, also try adding 2 CPu if you haven't tried it already. Regards Jörgen2

Hi, You should be able to do that with the Remote Control, there you can set the Remote Control settings so that you can remote control it even if nobody is logged on.. Remote assistance will only work if a user is logged on, remote desktop only works if there is no user logged on. So remote control is the way to do it. Regards, Jörgen

UEFI machines are tricky to boot, what hardware are you using? the HP elitepad 900 for instance is a pure 32 bit tablet and it requires a 32 boot image as it cannot boot from a 64-bit boot image. So as Niall wrote you need to make sure that you have a task sequence that supports UEFI partitioning, and that you use the correct architecture that matches the device for boot image and so on. And as you wrote you have already the DP's running server 2012 so then you should be able to support pxe booting 32 bit UEFI devices as well. Regards, Jörgen

Hi, Why have you created it using Gimagex? have you run Sysprep before the capture? I would redo the capture using the capture media in SCCM 2007 and try againg. Regards, Jörgen

Hi, What options have you setup at the Sync Options?

Hi, Is the error displayed on a newly installed server or an already existing? I would start with checking if the boostrap log file is on the server in question on the C:\ drive. If you check permission either for the service acciount you use or the site servers account, check firewall for issues. That is where I would start. Regards, Jörgen

hI, Make a policy with the setting you want to change for the VM's, policies merge in ConfigMgr r2 for exclusions and so on so you can still use the same exclusions as you have for the Operating System.Then deploy it to a "vm" collection with the setting you want to change perhaps scheduled Scan for instance. Regards, Jörgen

Hi, It means that it isn't tested yet. so I would hold off until an official announcement is made. Regards, Jörgen

Hi, IP helpers are required if the client is not on the same network as the server holding the DP(PXE enabled) role, the same as a normal DHCP server. So you need to make sure that IP Helpers are configured, is it the correct server that answers the request? it looks like a WDS server which have admin approval enabled which is responding. Regards, Jörgen

Hi, have you set the task sequence to "access content directly from DP" then the you must use a custom made client installation package because the builtin is read-only. Is it for all clients? otherwise check your boundary and boundary groups as well. Regards, Jörgen

Hi, If it didn't join the domain, check the Netsetup.log file on the client as well to start with. It will give you an indication on why it wasn't joined to the domain. Regards, Jörgen

Hi, That is correct, you should only use Windows 8 drivers for WinPe 4, If you use HP or Dell they have WinPE Driver packs you can download and import and use in the Boot Images. Regards, Jörgen

Hi, That is the way to do it! /Jörgen

Hi, You mean that you should only prompt if the computer is unknown? or how you should do it? If you should only prompt if the computer is unknown check the OSDComputername variable if it doens't start with "minint" then the computer is known. Regards, Jörgen

Hi, Check the WindowsUpdate.log file on the clients and make sure that the Local Policy that points the WSUS client to the SCCM SUP is correct. The SCCM Client on the compouter creates the local policy. Any conflicting Group Policy setting for WSUS would be seen there as well. Are there any errors in the System Status on the Site server for the Software Update Point? Regards, Jörgen

Hi, Are the computers deployed in the same way? member of a collection with a Software Updates deployment targeted to that collection? Any useful information in WindowsUpdate.log? does it use the correct SUP? Regards, Jörgen

Hi, I would guess Network access account or NIC/nework problems at it says that it fail to autheticate on all tries... /Jörgen

Hi, If you are using a Standalone media you need to add the OSDCOmputername variable when creating the media as well, otherwise it will not prompt you. Regards, Jörgen

HI, Some more information would be helpful as well, like which version of ConfigMgr are you using? 2012 sp1? R2?, are you using PXE boot or boot from an USB drive? Regards, Jörgen

Hi, All the PKI requirements are listed here: http://technet.microsoft.com/en-us/library/gg699362.aspx Here is a good description as well. http://blogs.msdn.com/b/scstr/archive/2012/05/31/step_2d00_by_2d00_step_2d00_example_2d00_deployment_2d00_of_2d00_the_2d00_pki_2d00_certificates_2d00_for_2d00_configuration_2d00_manager_2d00_2012_2d00_windows_2d00_server_2d00_2008.aspx Regards, Jörgen