Rocket Man

Why are you using the x64 driver pack?? There should be no x64 drivers available for these devices as they only support x86 flavour of win8.

Would it be possible to set yourself up with a console on a laptop or other physical device? If so you can then select the USB device as your desired media for the image deployment!!

You need to inject the WINPE driver into the boot.wim.

Is your client stuck in provisioning mode by any chance after it is finished the OSD? Have you tried it without adding the SMSMP and DNSSUFFIX properties? Is it the most up to date Network driver that is getting applied during the apply drivers task? Can you try this on a VM as this will rule out possible driver issue? EDIT: Also how is your office been deployed: only when a user is logged in by any chance?

I have experienced this issue before when using Intel NICs.......If I reverted back to the onboard Broadcom NICs it booted up fine. Also is this DC pointing to itself in the DNS settings and pointing to the PDC in the secondary DNS settings if it is multi site setup(Hub-Spoke)?

Considering the DP is enabled for unknown computers then there is absolutely no need to import the computer info into SCCM....any unknown computer that SCCM has no info on should automatically boot to a DP that is enabled for unknown computer support! Some organisations opt out of this configuration for security purposes and do have to use the import method but as mentioned if the DP is enabled for unknown computer support then no need duplicating work for yourself!! nectormjr any update on this issue?

Are your 500 clients not showing up in the new installation.....they should be regardless whether or not they have an non-SP1 client or none at all.......system discovery should pull them in as computer objects so that you can create collections etc...etc just like you would have done with your initial install of CM non SP1. If they are showing up in all systems have you tried a manual install of the new client and overwrite the older version on a single computer, without manually removing the old one first...just to see if they can communicate or not (I'd give this a go but not sure if it's best practices)....if it does communicate fully then simply redeploy the new client installations via the console out to the rest.

The way I deploy Java is to grab the msi and all other files associated with it in the temp directory after executing the exe file and create a package from them. See below: Then the program command I use is: msiexec /i "jre1.6.0_31.msi" ALLUSERS=1 /q /norestart Not sure if you need all files bar the actual msi but I kept them within the package just incase!!

Firstly have you created a new VM and tried PXE booting it? You haven't made any changes in the DHCP options? Have you tried removing the PXE service from the DP and reinstalling it? I have never had to reinstall PXE/WDS so correct me if I am wrong when doing this procedure. If you uncheck all from the PXE tab on the DP properties and apply. Wait for some time.....open up the wds console(If it still exists after the last step) and make sure that there is a yellow exclamation mark on the server node of the console. If this is correct then manually remove the wds role via server management. Restart your server.......check the drive and if Remote Install folder exists then manually delete it. Now this is the way I always set up PXE and have never had any problems. I manually add the WDS role from server manager first on the site system DP. Do not configure it or do anything in relation to manually configuring it in any way. Restart the server. Now enable the PXE options again on the DP. This will configure WDS for you and should pre-populate the extra directories and extra files automatically as you already have the boot images configured to deploy from PXE server. Give it a go and see what happens.

Are the extra directories created in the remote install folder of your PXE server? SMSBoot etc... Are the extra files inside the SMSBoot directory? abortpxe.com, bootmgr.exe, pxeboot.com, pxeboot.n12 and wdsnbp.com? Is your VM getting an IP address from your DHCP server? What is the error displayed when trying to PXE boot your VM? Have you tried redistributing your boot images? Is the WDS service running on the server? And lastly there is no need to configure anything in WDS when using it in conjunction with SCCM.

It should automatically remove the old FEP AV and then install the SCEP client. You have configured your policy to remove old AVs' before installing SCEP? It will not be able to automatically remove some AVs' but considering it's a Microsoft one....well it should, this is from my own experiences!

No bother....Kinda makes sense if you sit back and think about it.....you are trying to deploy an app during OSD and have set it to only deploy only if a user is logged on Which a user will not be logged on during OSD thus the reason as to why ConfigMgr does not make it available for selection in the OSD Task sequence editor!!

This is probably because you have set the criteria to install only if a user is logged on. Set it to install whether or not user is logged on. See below

If it is a batch file then create a package out of it...the program command line will be nameofbatch.bat. Attach this package after the setup windows and configuration manager step. Or as you mentioned use a run command line step and reference the packaged batch file package.

As far as I remember in server 2012 there is a flag that gets set to on if a server 2012 AD shuts down abruptly to prevent AD corruption if multiple sites are replicating with each other and the server gets started back up. I had similar problems with sysvol replicating between 3 server 2012 DCs that are sitting on a 3 node 2012 cluster whenever there was an abrupt shutdown and total loss of power....The problem was highlighted with a microsoft consultant and this is what our problem was.......the flag was reset and sysvol started replicating again....this may be your issue..

Just right click on your package node and create package from definition. Choose configuration manager client ALL 5.0 as seen below. Go through rest of settings when finished select package, properties and choose to copy to content share. Distribute package to DP(s) and change the default configmgr client in your TS to the new one.

Never came across this problem.....Have you installed any other software previously to doing the extra requirements? Are you sure the KB Update has installed correctly before it trys to install the BIOS update?

Are there any files-subfolders already inside the _Driver Packages Folder?

Is your SCCM server a member of the local admin on the server your trying to add PXE/WDS to?

So you have a server VLAN and 2 client VLANS. The 2 Client VLANs cant see each other, but they can both see the server VLAN. This should be no problem to achieve. In one site I have 16 client VLANs that cannot communicate with each other but they all can communicate with the server VLAN via ACLs with ports addressed to the various different services that the servers' provide. Your network Guys should know how to lock down traffic via ports to the your different servers!! You could start off with everything opened to the SCCM server and then gradually close ports that are not needed from client to SCCM and vice versa. You will also have to add IP helpers on both client VLAN switches to point to the PXE servers IP address so they can find it when they need to PXE boot. As for the ports that are needed by SCCM----->Client and Client---->SCCM heres a link

And the client is fully installed with your initial Task sequence?? (it may be stuck in provisioning mode which means it will not accept any new policies) You have created the configMgr client from definition?

SSRS on CM2012 SP1 works fine on SQL 2012 CU3, thats with SQL and SCCM hosted on the same server. I also see that SQL 2012 SP1 is also now a supported configuration as of Feb 2013. link

Considering there are no clues in the logs and all drivers are installed, have you tried re-arranging the last steps of your TS after the client gets installed? You could try and add just a single package/application (office 2010) if you havent already after the setup windows task and disable the rest including Install software updates task just to rule out it is nothing weird with the way your application groups are nested as you obviously have some validation attached to your groups to prevent/allow the different applications to install on the appropriate systems.

This is correct. Option 66 should be the FQDN of your PXE/DP server and option 67 is the location of the bootfiles. How ever if your DHCP server is residing on a seperate server than that of your PXE/DP and also the whole network is on the standard default VLAN then there should be no need to configure these options. If your network has more than one VLAN then you will have to configure these options along with IP Helpers/DHCP relays, network engineers should point you in the right path as to what extra configurations other than the basic DHCP options are needed to be specified in the ACLs'.

Just to be aware that I have imaged these devices in UEFI and standard BIOS by disabling the UEFI formating and partitioning task in the standard windows8 Task sequence and just using the default BIOS partition & Format task....... either way worked?? (I never checked the partitioning configuration in disk management after OSD with standard BIOS) By disabling the UEFI task and leaving the standard BIOS partition&Format task would mean that this device gets a standard BIOS as opposed to UEFI? Will check this out again if no-one can verify this? Its just that it takes approx 1.5hrs - 2hrs to image this device with some standard software (office 2013, Adobex3, java etc..) and will have to wait until the next batch comes in.