wmmayms

Hm I found that setting WDS service to delayed startup mode will often solve these kind of problems.

Last time i saw 80070002 it was about a file not found..

Administration Node --> Overview --> Hierarchy Configuration --> Discovery Methods Just rightclick any of them and choose properties.

Did you do a build and capture or did you import the vanilla wim directly?

Hm Déjà vu I have seen this problem from time to time.. sometimes its working sometimes not.. I would suggest you to try and update your wim so that you don´t have to apply that many patches, this seems to better the odds for a succeesfull OSD.. But I would be very glad if MS could get this solved 100% once and for all

Here is a guide on how to setup a secondary site: http://technet.microsoft.com/en-us/library/bb633289.aspx

I still don´t understand how you know if a client is corrupt? Do you get some kind of error message or do some functions stop working?

Yes there is a way, reconfigure them as secondary sites

To find the exact reason for this error would proberbly take a while (would surely involve alot of log digging).. Easiest solution is proberbly to setup a new DP with the exact same name, let it rest over night and then perform a clean demote.

You are right. Secondary sites do not require a local SQL installation. But they will still be needing to communicate with the parent SQL installation. This is done over this port. Here is a list of ports i used for a single site setup with protected DPs. I think these will cover your needs, but to be sure go through the list from MS. TCP 445 Server Message Block (SMB) TCP 1723 Point to Point Tunneling Protocol (PPTP) TCP 8530 Hypertext Transfer Protocol (HTTP) TCP 8531 Secure Hypertext Transfer Protocol (HTTPS) TCP 80 Hypertext Transfer Protocol (HTTP) TCP 443 Secure Hypertext Transfer Protocol (HTTPS) UDP 4011 Boot Information Negotiation Layer (BINL) UDP 135 RPC Endpoint Mapper TCP 135 RPC Endpoint Mapper TCP DYNAMIC, 49152-65536 RPC UDP DYNAMIC, 49152-65536 RPC TCP 3389 Remote Assistance (RDP and RTC) TCP 1025 & 1026 AD Login & replication TCP 389 LDAP UPD 53 DNS TCP 53 DNS TCP 139 SMB UDP 137 NETBIOS UDP 138 NETBIOS UDP 88 Kerberos Notes that this will also open up for Active Directory trafic.

Im guessing some error while communicating with your management point. i would start of by verifying DNS (make sure the correct server is answering when pinging your SCCM server). If this does not work i would check my network access account and then look into IIS and Webdav. Allso check for MP errors on your site system.

More ports are needed then the ones you mention. Im guessing SQL port 1433 is why its still in pending state. But go through the list and make sure you have all needed ports open.

Look at this post from Alan Burchill http://www.grouppolicy.biz/2010/08/best-practice-roaming-profiles-and-folder-redirection-a-k-a-user-virtualization/

begin by reseting all red components under component status.

80004005 is an access denied issue

Are all firewall openings in place? Take a look at this page: http://technet.microsoft.com/en-us/library/bb632618.aspx

Do you see any errors when looking into the status node for your site?

I change my mind. With that amount of clients and proberbly quite a few vlans it would make sence to setup a multiple site setup. Without knowing to much of your companys infrastructure or wan links i would suggest a central site for handling OSD/Updates/Reporting and all other common stuff. Then you could setup a child site for every department desiring to administer their site on their own or where wan links are bad. At child site level you can then delegate rights for department administrator to add custom applications or what they might need.

Child sites will get all packages/collections/advertisements etc from parent site. They will not see anything from another child site on the same level. How big is this company? How many diffrent departments do you have that might be intrested in administrating a sccm site? Im not convinced that this is the best solution for you.

Look into the smsts.log located here %temp%\smsts\smsts.log (press f8 after starting the ts). Proberbly you forgot to distribute a package in the ts to a distributionpoint.

I havent read through all the post. But im guessing you are after something like this :-) select volume 0 assign letter=d select disk 1 online disk noerr attributes disk clear readonly noerr clean create partition primary noerr assign letter=e noerr format FS=NTFS LABEL="Application Volume" QUICK noerr select disk 2 online disk noerr attributes disk clear readonly noerr clean create partition primary noerr assign letter=f noerr format FS=NTFS LABEL="Database Volume" QUICK noerr select disk 3 online disk noerr attributes disk clear readonly noerr clean create partition primary noerr assign letter=g noerr format FS=NTFS LABEL="Transaction Volume" QUICK noerr select disk 4 online disk noerr attributes disk clear readonly noerr clean create partition primary noerr assign letter=h noerr format FS=NTFS LABEL="Bank Volume" QUICK noerr exit Commandline in task seq: diskpart /s "%scriptroot%\Custom\DiskPartSCCM.txt

Hm hard... I guess you could try looking into your dism.log But before doing this i would proberbly try reimporting my driver and then recreating my bootimage. Of course if you havent done to much customization to it.

How do you know if a client is corrupt? What happens? I think it best to find the root cause

Create a commandlinestep in your TS and select "run this step with the following account". Should work if you specify "localhost\account"

Great Post! Thank you