willisj318

I checked that out, it has some more information thank you, but for example the PE steps it is blank as to details of what the step is called etc. This is better though.

There is a report in 2007, Task Sequence - Advertisement status > Status summary of a specific TS. In 2012 the corresponding report is there, but lacks the detail, it just says if the step was successful or not. Does anyone know of a more detailed report for task sequences step by step? I've looked through them but might just be missing it.

Are you opening it on the other machines as your ID or their ID, and if their IDs did you give them rights in SCCM? Also makes sure the console version installed is the same version as SCCM.

It sounds to me like you simply need a separate collection and deployment going to servers that you have set as available instead of required? Unless I am not understanding what you want exactly.

Basically it is called servicing. You need a Software Update Point in SCCM (which works in conjunction with WSUS). Once the SUP is working you can go in SCCM to your OS Images and do what is called Schedule Updates. This schedule runs and updates your wim file for you, then updates the DP for you. Your SCCM does not have to be your WSUS Server, but it does have to control the management of the updates. i.e download and deployment of them. I haven't got that far yet with my 2012 environment but will hopefully be there in the coming weeks.

Is the 2nd user logging on and will permanently use the PC? If not then licensing shouldn't matter.

I would work to get that working instead of simply axing it and moving to an old version. 2012 and WSUS does work, we have it running in the lab. Make sure WSUS is configured properly would be my guess.

The problem with this is 1 it takes time to uninstall, then when the original user logs back on it has to take time to install again. Like Bendes said, app-v is the way to go. Why is this a problem exactly if I may ask?

No it isn't compatible with Server 2012. WSUS 4 is needed for Server 2012. You can use WSUS 3 sp2 with SCCM 2012 if you are using Server 2008.

I don't know of a way, if there is I would like to know as well.

Yes, make the deployment for the application mandatory and select the option for it to Not be available in the software center.

On your step where you apply the setting, you can create two of them, on one only have it run when it finds a battery via WMI Query. Select * from Win32_Battery where availability > 0 Have the other run when it does not find a battery Select * from Win32_Battery where availability < 1 You can set up separate collections and create a task sequence variable to use as well.

It doesn't look like HP supplies a Win 7 driver for this. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?cc=us&prodNameId=1847704&prodSeriesId=1847703&swLang=8&taskId=135&swEnvOID=1093#11360 You would have to find the driver and import it into SCCM, or create a package for it if you wanted the additional "features" ATI gives you. Maybe you can tell the PC to scan MS for hardware drivers somehow, but I don't know how to do it if so.

I'm assuming this process errors at some point? Is reporting set up? If so, I would see what that says. But, maybe there is a better way, but here is what I would do. Enable command line support on the boot image. Create bootable media to a memory stick. Use this to boot. Have the command prompt open (F8) let it go until it errors. copy the SMSTS.log to the memory stick, investigate it and post it here. http://sccmguy.com/2011/03/29/where-is-the-smsts-log-located/

I'm fairly certain it still copies the client install to C: but try this in your path, PATCH="%_SMSTSMDataPath%\OSD................

If you go into the properties of the boot image itself, Windows PE tab. Does it list the drivers in there that you removed? If so, what if you remove them from there then update the DP? I've had to do this before, when removing them outside of the boot image didn't actually remove them from the boot image. I can't comment on it always getting larger though...

Administration > Site configuration > Severs and site system Roles > Properties of the site system role

In my experiences I had to make sure you went through SRS and configured it for use with SCCM. Once I did this, the instance showed up.

You can do it like anyweb, or copy the directories to the wim. We chose to copy them, they aren't that big in the grand scheme of things, and who knows if we will need them later down the road. For 64 bit you need to disable 64 bit file system redirection for it to work.

Note, I dont use MDT integration. But this is really easy in regular SCCM, espeically if you format the drive every image. Scrap the batch and run the command line. In the task sequence, the command is 'bdeHdCfg.exe -target default -size 350 -quiet' and it automatically targets the OS drive. Start In should be %windir%\System32\ If the drive is already prepped for bitlocker it skips it. I personally hate running things in batch files when there is no need to. Like in thi scase. The SCCM report and SMSTS.log will show you any errors for this task. Also make sure you check the box to Disable 64 bit redirection still. I also set a 15 minute time out just cuz. If you really want to run the batch file, for 64 bit try \Sysnative\ instead of System32. %windir%\sysnative\bdeHdCfg.exe -target default -size 350 -quiet Note also, the 350 is needed for Win 8, 300 is fine for Win 7. We use MBAM so we dont copy keys anywhere. Sorry I cant help for that.

Of course it does. When creating a master image, make sure your .net flavors are installed, run windows update, it updates. Capture image.

We need to know more info, for instance the link speed or how the connection is to the main office. Locations around the world. What type of work needs to be done at each site?

I did this in my lab, it works fine. I guess it really depends what you want to report against and all that. <--- This is pretty much how we do it for 2007 as well. We deploy one big updates package to an update collection with anything that needs to be patched.

What Rocker Man and Xist said. Also check your sccm report "Task Sequence Advertisement Status - Status summary of a specific task sequence advertisement", if thats not the report you are already looking at. This report should show you what step it is stuck on/currently trying to run, and hopefully give an error.

How far does it actually get in the process? Does it boot and try to load the boot image then fail? Or does it not even get that far? Put the boot image on a memory stick and boot with it. I find this is a good way to get errors and troubleshoot pxe issues. Yes it bypasses PXE, but you can 1. see if it finds its advertisements and 2. you can pull the smsts.log file and look at that for clues.