Rocket Man

Is it the same PCs that are failing or different PCs all the time from that collection? From your symptoms (half will fail) then I gather the others are successful....then it may be some underlying problem with your internal network/PCs hardware?? Have you tried to isolate these problematic PCs into a seperate test collection and try the same TS out to them?? (See if any of them are successful)??

How do you mean swap out your TS?? Generally what I have came across myself is that lets say a deployed TS has successfully/unsuccessfully been deployed to specific target collections and I run the OSD report then choose the TS option within the report it will show all the information for this specific TS and collections......if you remove this particular advertised deployment and then run the report again you can not select the TS from the options as it has been removed so thus clearing the log info on the report...is this what you mean by

Remove the deployed Task Sequences should clear the report..

Ok so it is a VM that this is occurring on..right? Can you not just delete the virtual NIC and recreate another one for it?? This way it gets a different identity......maybe it's the current Virtual NIC that is corrupt.

Firstly it is not the size of of the HD that is the problem not unless of course the 120Gb is fully used up....is it? You can capture an image on any size of HD.....and redeploy it back out....size is not relevant not unless the 120GB is fully used up.....and then you are trying to deploy it to a smaller HD which is a problem.... In your TS is there an apply data image component along with an apply OS component?? If so you have to move the apply data image above the apply OS component.....the data image is the system reserve as you see in the above snippet....then on the apply OS component...edit it and edit the partition so that the primary OS partition installs on the rest of the partition...i:e change it to 100%

So just to clarify you have a particular remote site that you have successfully achieved some client installs on and some that are not installing also on the same site...... is this correct?

and you are sure file & print sharing and WMI is allowed on the local clients firewall??

What method are you installing the client by....Push..update..or manual? Is there any sign that the machines are even getting the client advertisement...check this is Task manager...services there chould be a ccmsetup.exe service running... Where these machines alrady existing on your network/AD/DNS infratstructure prior to implementing SCCM......if so I have came across this problem umpteen times before and my solution is simply to delete the DNS records of these problematic PCs from the DNS console...reboot the PCs so they get a new DNS entry and try again...this has worked for me as I said many..many times..

I take it then that you are not the only systems admin using SCCM as if you were you could manually keep track of what has been deployed and how many off etc... I think you could create an adobe specific computer collection with your 20 computers in it.....deploy adobe as part of a individual task sequence to this collection and then also check the disable this software on deployed computers in the program properties also of the package (this will prevent it running on the PCs again)......then I am fairly sure with a bit of tricking about that you could have a query associated with the TS that it will only install on this adobe collection.....so if this TS is deployed to say other collections it will not install as the query does not have entry for the other collections.......but again it is down to SCCM admins to keep control over these licence specific software deployments....so in other words if you do get this to work then these software deployments should be only deployed via the TS with the queries configured and not via the software package/program method Hope this helps a little.

Is there a trust between these DCs... Are they replicating their namespaces with one another? If not then no need to demote it just wipe it fully including all other roles....just set up DHCP and other roles from scratch on your 2k8 server.. then rebuild the old server with server 2k8 If they are syncing with each other then yes of course you have to demote...it's cleaner and get's rid of any old entities with the DC.

In your task sequence how are you naming your OSD computers?? Just out of curiosity..have you searched the all systems by typing in unknown?? Do this and there should be only the 2 built in unknown objects(x86 and x64)...if there are more then delete them... There should be no reason why you cannot deploy over and over again to unknown once the system account has been deleted out of the SCCM DB..

OK....remove and redistribute the boot.wims from DP..and try again....and also make sure the extra directories(SMSBoot x86 x64 + files inside are created in REMOTEInstall folder)

Dont mean to bring up an old thread...but has anyone any ideas what the solution could be on this problem?? I have found out it is not the Legacy NICs as I thought as I have deployed to physical machines and still the same outcome Thanks

I have one question why are you trying to B&C and hold onto network settings...it does not make sense as the final image will have the same IP address if you do get it to work successfully...then you will deploy this to others machines and you will have alot of IP address conflicts..(I can only assume that this is what will happen)... I can't see an obvious way around this...other than setting up DHCP and as you have suggested yourself would be away much easier.. Could you just not deploy a standard image deployment TS form a capture media to target machines that have static addresses etc...and in this TS capture network settings etc...at the begining of the TS.....now this will work for you and you do not need DHCP!!

Unknown computer support is a major component of SCCM....without it you would have to fully configure all Out of the box PCs..join to domain etc.... get the client installed before you can do anything with them with regards to SCCM(bar importing system info of course...which can be time consuming).....with unknown computer support all you have to do is physically connect the new PCs tp the LAN and F12 them for PXE boot...simple as that......if you boot a known PC it will not take a PXE advertisement...this is the total security of Unknown Computers.. EDIT: it will always be the client you try and re-seat the RAM in....do not know why this is the case but it has worked for me before on lots of occassions!!

For OS it is File and Print sharing and also WMI......dont worry about endpoint it will install once policies are created and deployed......follow Niall's guides from the start and you should have no problem

Yes file&print sharing and WMI needs to be opened on target machines in order for the ConfigMgr Client to install

Hi By deleted do you mean you actually deleted the REG KEY??

Can I ask why you import data into SCCM for these laptops?? If they are new then they are already unknown to SCCM......just deploy the TS to the unknown computer collection and f12 boot the laptops.....(once the DP is configured for unknown Computer Support of course) I have seen this error before with my old WDS and most of the time the fix was to re-seat the RAM modules in the system...

Hi Is it possible to store packages in the APPCatalog as one of the above members has quoted?? I did set it up in one of my test labs and was able to log into the site and everything but I never went much further than this as I thought it was only for APPs and not Packages........At the moment I am using only packages..

Yep installed a PS supporting 15 Remote DPs and seeing the great benefits it is producing...of course after following your great guides to setting it up.....Have also installed a PS configuration of SCCM 2012 at 5 single sites and SCCM 2007R3 1 site......Awesome piece of software and really had no experience with it until recently....great asset to have running on any network.!!

Do not know of any off hand but I do know the previous version had to be installed on a Physical box ..VM wont work apparently..(not unless DPM2012 has overcome this which would be a massive bonus cost wise) as the older version there required 2 RAID sets to be configured etc... Hopefully someone will post a link as I would be interested also in seeing the setup methods and if the above is still the same.

EDIT: Also just to warn you by just deploying the install.wim from the RTM media will install the OS to the D:\ drive on any machine (this is a major flaw with windows7, apparently windows 8 has overcome this!?)....to get it to install on the C:/ drive of any machine you will have to eventually get a capture TS successfully done...either by the B&C or by a standalone capture media...either way works. But just for testing carry on for now with the RTM install.wim....then you could install all your custom software and then simply use a capture media TS to capture your custom wim.. OR If you have all your software packaged then just roll out the install wim(if you cannot get your B&C to work) and then do whatever mods you have to do and capture it. It is also reccommended that all this is done on a Virtual environment as it will have minimum drivers etc.....thats if you do intend to package model specific drivers?

OK this is where you are going wrong......The build and capture with all source files is specifically for BUILD&CAPTURE and not just build.......... disabling capture steps will not work thus your missing BOOTMgr...if you want to just build a machine then create an OS image out of just the install.wim from the sources folder and create a new TS this time using an existing image and not the B&C task sequence....the wim file is all that is needed to achieve this...once you have created the OS image. When you get your B&C working properly and you have your captured custom wim file then you can create a new OS image from this wim file...but for now you could use a standard RTM wim file and see how you get on!!

It will work!!