murda

Thx for pointing me in the good direction. Final question about the DP's. Can I add more DP's on the same server? example: Standard: E:\SMSPKGE$ an extra share for DP: D:\SMSPKGD$

Yes, I know how this can be done. But how can I create a custom DP for certain applications? Is it under "site system" - rightclick - "new" - "server share" for creating a new DP? Normally DP's are auto made on the HDD with the most storage space. Anyweb, is it normal to make more DP's depending the use? Or do you work with the standard DP's?

Hmm how can I disable windows vista performance check because it runs everytime when I deploy a Vista image.

How do you guys setup and manage DP's? Do you all have a seperate DP for images,bootfiles,software,updates,... or just on DP that combines everything? Now I wanna move my existing DP's to a different share that's not on the same PC. How can I change the path of the DP so I can point out towards the new DP and copy the packages towards the new DP? thx!

Where can I find more variables like "timezone" with the matching "values" ? Is there a list on technet?

The script has to been run on the serverside or ... ?

Oké this question has been answered.

An additional question. I captured an ACTIVATED vista OS that was been prepped. Now when I deploy to another laptop, the OS isn't activated ... (we are working with KMS server) Question is should I generate a newSID when deploying the vista base image??? And then activate my machine on the KMS server?? Or is this newSID generated when you deploy your base vista image? sidenote: normally we ghost our new vista laptops and then execute a batch file that generates a newSID,reboots and activates vista towards the KMS... so the question is do I need to generate a new SID everytime i deploy an new image? I know we had to do it with ghost or when we copied a VM.

I will and I'll get you updated. Some question seems to be logic but I am on a time based project so I am not able to test everything and thats why I ask questions that maybe seems logic to the pro's Only started with SCCM 3 months ago but its been a steep learning curve

hi anyweb, This could be my problem! thx for the heads up.

Hi, I just installed Vista Enterprise from DVD. I configured some options like language,keyboard layout, desktop image and so on... I copied the prepped profile towards the default profile. (also tested to see if it worked when i logged in with another account) Next step was creating a capture media cd for my laptop and a hour later my system was captured. I configured the captured vista.wim file in sccm and build a TS with the captured image. So far so good and the TS has been applied towards the laptop and was fully installed from SCCM deploy. Now i see that i forgot to set the IE options: homepage & proxy etc... Can I fix this without rebuilding a new image? Can it be fixed with an unattend.xml, this can be set in the TS - apply operating system - use an unattend file ... for custum installation ?

Lost track of this thread but I stopped trying to install my vista on a bare machine and then capture it. I just prepped an vista image and then used the capture media cd from SCCM. So far everything works.

On some vendor websites there are faq's on how to install with command line. (like intel vga driver, bluetooth drivers etc) Also sometimes the "/?" can help. As it gives you the available options on the switches.

I'll try that and see if it works

Anyone care to explain me the advantage of using security groups with computer names or usernames for software deployment trough AD? All of our sec groups are applied with usernames. My boss wants the same with SCCM. What happens if an admin account take over a pc from another user. I can imagine that the software for Admins are going to be advertised towards the pc or can I prevent this?

After installing the new R2 in SCCM, the following error occurred when booting trying to boot PXE. My solution was: Check your C:\RemoteInstall in the SMSboot folder that the PXE files have been copied. Try to boot in PXE again.

Anyweb, Perhaps you know how to deploy multiple applications (software) in one task sequence working with variables? If you would care to explain to the community?

Take the X64 boot image and import your x64 network driver for that particular pc where you want to install the OS. Update the DP of the x64 boot image. Try again and see if that works. You can do it with X86 boot image with a X86 network driver but you'll have to import the right X64 drivers in your task sequence otherwise it won't boot anymore after it applied the OS with a x86 network driver. Enable command prompt support in your bootimages. When the task sequence begins you can press F8 and try ipconfig to see if your test pc gets an IP. (before you begin clear last PXE advertisement in the collection of your test pc) ps: did you import new computer association with the correct mac adress and bios guid? If this pc already is in your main collection then delete it and add a new computer association because otherwise it would conflict. (2 pc in the collection with the same mac and bios guid in sccm wil conflict with your pxe boot)

Nobody that can see whats wrong with the capture with the applied log files?

Tried bot 32 and 64bit boot image. Always the same error. Created new task sequence etc but no advance. Guess I am stuck now. edit: log files from my failed capture task included. smsts.log smsts_.log

Capture the reference machine Join workgroup (joining domain - OU with admin credentials) prepare configmgr client (changed nothing) prepare OS (changed nothing) Capture the reference machine (filled in UNC path of the SCCM share for capturing the OS and filled in the domain admin account) Thats about it.

This is my tasksequence but i removed the "Build the reference machine" part. What I am trying to do is capturing a regular pc in the domain using pxe boot. I thought it was possible Maybe that's why i am getting these errors ... I am just trying a regular "Build & Capture" and it is currently formatting disk C and it failed bringing the pc in the domain. Seems a network driver issue.

I will try your suggestion later.(if this step below doesn't get solved) I am one step forward now. I set the Network acces account as domain account. This let me go one step further in acces rights towards the share. Now I am getting the following error: Task Sequence: Capture "name" has failed with the error code (0x00000032). Here is the log file. smsts.log

server log: (smsts.log last entry on 25th is done manually by running TSmanager.exe) smsts.log smspxe.log distmgr.log

client log: smsts.log