Rocket Man

By resolve you mean ping it etc.... Yes able to ping it both IP address ping and DNS name ping no problem..... if i enter in the site server name to browser URL i get the IIS page also...(these VMs are on a remote site than my PS server) Connectivity does not seem to be the problem. As i have said the workgroup VM does have a signed cert....... it is in all systems as active...but it does not have the full client, remote control etc...even though in the general tab of the client it say all components are installed.. Maybe it is because it is a VM with 2 NICs, one for PXE booting (legacy NIC). I am confused especially with connection to site server, and site code is also found by client but when i try to discover site in the client options in control panel it fails. Rocket Man

Good stuff!! Just a tip...you do not need to set DHCP option 60 and 67 if your DHCP server resides on a seperate server other than your SCCM/PXE server!! Rocket Man

The x64 is a normal process.........I think your PXE is not set up properly when it still asks for a f12 after recieveing the PXE advertisement. The only time it should do this is if and when you have advertised available(not required) OSD task sequences. Once f12 is pressed then it will give you a the list of task sequences to choose from. You are making this process you are trying to achieve required and not available?? I have asked is your DHCP server on the same server as your SCCM/PXE service point? Rocket Man

Ok Thanks Peter I just checked the client on the machine and actually it does have the self-signed cert but is still unable to find the site(it has the site code though)....and still only half the client installed without RMCCTRL service in task manager etc.... I am testing this on a batch of virtual hyper-V machines with a legacy NIC attached also....would this be the problem? Unfortunately i can not deploy to physical machines to test if any difference.. I checked the above log and the only failure i see is CCMCreateAuthHeaders failed (0x80004005) and failed to open to WMI namespace '\\.\root\ccmvdi' I also added these parameters to the client setup SMSLP=Server.domain.xx FSP=Server.domain.xx Still nothing! Thanks Rocket Man

Hi thanks for your help....the above did not work for me but did give me a good starting point....have it working the way i need to now... Thanks again Rocket Man

Create a run command line task sequence and enter in cleanmgr /sagerun:1 this will automate the clean up for you!! if the above does not work you may have to use this instead C:\Windows\System32\cleanmgr.exe /sagerun:1 Rocket man

Specify which boot image to use during the creation of your task sequence!!! In other words create a new task sequence and point it to your new boot image!! Rocket Man

No this is the way it is.......You will have to create a script that checks the local time of the PC and if it is in a time frame then shut down...if not in time frame ignore but it will still recieve the advertisement like you are getting now but will not shutdown as it is not in the specified time frame... this is not bible but is a brief example, get a person who can script to make it work: If Time (hr) = 17hr And Min time <= 30 then (%systemRoot%\System32\Shutdown.exe /parameters) End if So in the above example if the machine is on between 5pm and 5:30pm and recieves the advertisement then it will shutdown If the machine is off at this time and is switched on anytime after the specified times it still will get the advertisement but will not shutdown. This is just a guide and the above code will not work...but this will give you a starting point...and do get a person who can script to achieve this and you will have your powermanagement working!!!!!! You can use the windows shutdown exe to shut down the PCs.......in the script point it to the shutdown exe and have your time frame specified. Rocket Man

Think you are trying to capture the wrong way!! First of all you dont boot the reference machine to PXE to capture it....you only boot to recieve an OSD deployment triggered via SCCM task sequence. Have you never created a capture media CD/USB? Basically you do this via the Task sequences node. Once created you have your reference machine logged into windows and you run the CD\USB directly in windows......this will sysprep the machine and then continue to capture it to designated directory specified during the initial setup of the capture media!! Do you not do it this way?? Rocket Man

Are your boot.wims distributed and configured for PXE? What do you mean by this?? Rocket Man

It is to an unknown computer that you are trying to deploy an OS to?? when you recieve this error it normally means that SCCM knows the machines identity and has it is the database. Thus not allowing it to recive a PXE advertisement. Just another thing I take that DHCP resides on a different server than the SCCM/PXE server? Rocket Man

Hi Peter I have done this and now it does not bomb out....just wondering is there is some setting that I have to attach to the Setup Windows and Configuration to get it to install the full client...at the moment it is only installing half the client.........the WORKGROUP PCs show up in all systems as active and clearly shows they are in a workgroup in the properties of each. I have added SMSMP=SERVER.domain.xx to the Setup Windows and Configuration settings......but still only half client. Any ideas or is it not possible to fully manage workgroup machines? Thanks Rocket Man

What error code is the PXE giving?

No i need a standard user...thanks Will try this tomorrow Rocket Man

Hi Does this make the user a standard user with no rights to the local machine?? This is what i need to achieve! Rocket Man

Hi Is there a way to create a sandard user and set a password during a workgroup OSD. basically i have an answerfile that will create the local admin account and set the password which i created in WAIK. I can create domain groups on the local machine with the following command cmd /c net localgroup "Administrators" "domain\securitygroup" /add Is there a simple command like this to create a new standard user that is only a member of the local users group and also set a password at the same time? much appreciated Rocket Man

It is the way to go....now especially you have sufficient HW at remote site to set up a decent DP. I have a PS and 15 remote DPs on Virtual hyper-V servers acting as PXE service points and so far all working very good. So i have 16 Boundaries each with a DP group assigned to each Boundary. Rocket Man

Is it the same firewalls at all sites??

Yes A remote DP would probably be best, but as Jorgen has highlighted it depends on your enviornment. How may clients at the remote site do you have, if virtual platform such as Hyper-V is available on remote site then you could run DP on a VM and this way you can use the PXE functionality from the DP. A windows 7 client acting as a DP does not support PXE. Rocket Man

Have you specified to allow program to run via TS in the properties of the package? Are they deploying via program deployment? Also how is your IIS setup...have you added all the prereqs?? Rocket Man

Direct Quote: http://msandbu.wordpress.com/2012/05/30/sccm-2012-cas/ "Microsoft says the following about it” The central administration site coordinates inter-site data replication across the hierarchy by using Configuration Manager database replication. It also enables the administration of hierarchy-wide configurations for client agents, discovery, and other operations. Use this site for all administration and reporting for the hierarchy” Must be only able to add one reporting service point in the hierarchy....you have already done this on your PS!! Maybe someone else can verify this?? Rocket Man

To start with What does your component,site status and distribution point configuration status look like in the Monitoring node?(all healthy with green ticks)? Is the WAN links between the 10 sites that are successful and the 6 that are not successful any different in bandwidth terms?? How exactly did you set up the remote DPs? Rocket Man

What commandline are you using? Easyway: use OCT to create your custom MSP file. Name and save the MSP file in the root of the office 2010 folder. Create your package and the commandline is setup.exe /adminfile xxxx.MSP Rocket Man

It should not take any longer than an hour for the above to kick off, considering you left the client policy poling at default which is 60 mins.........The reason as to why it is seen as past-due is because the machine in question did not recieve the advertisement before the deadline(it recieved it after the deadline)...once recieved it should kick off automatically within an hour or so approx.. Rocket Man

Any reason as to why you have changed the account that connects the MP to the SQL database from been the local computer account to been a domain account?? Is this a prereq for SMP? Is there any client communication at all on your sites back to MP? How is software deployment etc...at the moment? Is windows authentication enabled in IIS? By default it it is not and anonymous authenitication is the only form of authentication...by standard I always enable windows authentication... from your remote sites verify that you have access to your PS IIS website by opening up a webbrowser and browsing to the name of your site server e:g http://xxx-xxx You should receive the IIS webpage.. Rocket Man