jeaostro

Hi. At one of the locations we have a RODC (Read only domain controller) and we would like to automate the deployment here. At that location we also have a Secondary site. I have looked at the following post http://myitforum.com/myitforumwp/2012/06/25/offline-domain-join-with-mdt/ in the section Offline Domain Join – Automatically using Unattend.xml but it requires a Web service that we do not want to implement. It is stated that this can also be solved with a script, but I cant find such a script. Has anyone solved this in another way, or do you have such a script? Thanks a lot for the reply.

and yes you will need to push the content to the secondary site DPs. Move the boundaries, Then upgrade the clients so that they are assigned to the secondary. How many will there be at the secondary site?

How do you want the 2012 hierarchy to look like? One primary and two secondary sites?

Now

will be possible with SP1 for sccm2012. but not noe.

Hi There are no issues having a Master FEP policy for all servers. Works just fine, but do not exclude to much. Having a dedicated policy for hyperv and Citrix is a good ting.

Should i attach some sort of log?

also after the redeployment with the patch option, the computer is not set to Obsolete=yes in the sccm console.

Hello anyweb. Is this a supported solution for patching up the SCCM client with hotfixes during OSD? I tried this with the hotfix above and it worked great for a OS deployment on a "new computer" (a computer that does not have the sccm client), but when i redeploy this computer it hangs on the Windows update step at 0%, and when i force a reboot i see the following error in the sccm console: MP has rejected a message from client GUID:B73F2B74-4921-42E9-83D1-DC71150CC480 because it was signed with a public key that does not match the key published in the database. If i redeploy the client once more without the patch= option the computer deploys as it should. The workaround now is to delete the computer in the SCCM console, and import it again as a new computer, then there are no errors.

Hello First of all, you dont need disable the multicast feature to run a unicast. Just change the advertisment to run everything from DP, or create a advertisment just for Multicast (to a collection) and other advertisments to another collection for unicast. Or do not set the OS image to be multicast enabled. Second: The "error" you describe is a common issue (seen this on 4 different installations where Multicast is in use), and Microsoft has knowledge about this. Do not know if there is a fix anywhere. So you have to make a choice: 1. do not use Multicast (remove the PXE role, then remove Multicast, and WDS, afterwards install WDS and PXE roole again) 2. Have multicast enabled, and create a advertisment for Multicast and another advertisment for Unicast. Hope this could shed some light

XP doesnt support major HAL changes, this will lead to BlueScreen. Like Sata changes, or CPU Singel/multi core changes. This can not change from the system captured to the system deployed. Is my understanding.

Hello What about using a Protected Distribution Point? Then the hierarchy wont crow and become more complex. You can deploy the PDP from the Primary site.

hello you might have som pending reboot entries in registry, known issue for similar problems. Or you can try to kill msiexec processes running on the computer? if any.

some sort of MAC adress filtering may also be a solution? The dual PXE solution: http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/99/language/sv-SE/Default.aspx

Also. You can configure a delay: By default, the Configuration Manager 2007 PXE service point is configured to respond immediately to network PXE requests. You can configure a delay when setting up the PXE service point if there are multiple PXE servers on your network so that the Configuration Manager 2007 PXE service point will wait the specified amount of time before responding to network PXE requests.

Hello Andreas It is possible to "hack" the PXE solution, so it will give you a PXE boot menu where you can choose from what PXE solution you would like to boot from. Not supported of course, but possible. I can send you some information if this is something you might consider.

hello Look at the attached files for key selling points. Config Mgr.pptx Deploying Windows 7 with System Center FINAL.pptx

Hello beben Not a direct answer to your question, but I do recommend you use a Protected Distribution point on the smaller locations. You install WDS on the server on these locations and PXE service role on the Protected Distribution Point that is assigned on the servers. This will result in that the OS deployment run within the protected distribution point, and not towards your Primary site. The clients boots towards your local WDS on the locations, and gets all the packages from the Protected Distribution Point on the same locations.

Thank you very much! Saved me a lot of time Do you also have a report that showes disabled and enabled users i Active Direcotry sorted on OU`s? If possible the computer the users are "primary console user on"

Hello You might get this message pop up because one of you packages forces a reboot. In update Retriever look if any of the packages has the reboot type: Forces a reboot. Try to set these packages in Status Test, and run a deployment. Please let me know if it works.

Hello Isn't C:\drivers a vendor driver folder? SCCM does not create a c:\drivers where it downloads all the drivers from the driver package buy default? Does this also happen if you format the drive, then test the deployment? DO you use the auto apply driver step in the task?

I have done this the following way: To steps in the Task Sequence: 1. Copy HP SSM to Client: cmd.exe /c xcopy.exe \\server\SMSPKGD$\P0100054\*.* c:\HP\SSM\ /E /D 2. Run the HP SSM client: cmd.exe /c SSM.exe \\server\packages$\HPsoftpaqs\ /A /F /Log:\\server\Logs$

Hello You can use HP SSM and HP softpaq download manager to manage drivers for all the HP computers. Add HP SSM as an application and use it in the Task Sequence with the correct parameters. Then you only have to specify the models in HP Softpaq download manager and download the drivers there (driver repository), no work in SCCM. Then it is easy to add new HP models. HP, Lenovo and DELL have solutions for this, and they work like a charm. If you add a Intel driver, this intel driver can contain drivers for a lot of Intel network cards. If this is not Intel i have seen posts that other brands have drivers for WindowsPE, and you should not use the Windows Vista/7 driver. Import Only network and Sata drivers into the "driver database" in SCCM, and add them to windows PE boot images. Sometimes these drivers are not beeing applied to the Windows image in the task sequence (auto apply driver step) (plug and play id "error" so they are not applied) Use driver packages (does not have the plug and play weakness) in the Task Sequence for the different HP models, and remember to use wmi queries on the driver packages step. Please don't have a lot of driver packages step in the task sequence without wmi queries on the option tab for these. You can create a driver package and only point it to the root folder where you have all the drivers for the model, you do not have to import the drivers into the driver package. If the project is about to be unplugged i recommend you contact a Microsoft partner that can help you get this up and running 100%.

Hello oliphanj We are trying to complete an automated driver solution, so that you do not need all those steps in the task. We just run dsu-cli step in the task towards a local driver repository and the client will download all the packages that applies to this system and install them.

I cant find where I can edit the install parameters? Properties on the package doesnt give this option :/