lightiv

Thanks, this appears to have fixed my D drive OS issue.

Have you actually deployed the files/package for JPM00023 to the distribution point?

Attempting this with VMWare does not work but trying it on a real PC and I make it to the TS Wizard Password screen. I guess this is MS' way of getting me to use Hyper-V?

I seem to have this working...PXE boots and then when Windows tries to load I get an "error loading HAL." This is particularly confusing since I am using a virtual machine (VMWare). How can I have hardware issues?

Thanks, this stopped the error message I was receiving in SMSPXE.log. I have to ip helpers for the actual PXE Boot. What is the correct boot file name to 67 on the DHCP server?

Thanks for the guide. I successfully upgrade the Server and Clients to SP 1.

Ok, I now understand what my issue is here. The reason the Software Update Group (SUG) is not being created is because of the "Last 1 day" setting in the guide. There has been not updates released in the last day so there was nothing to add to the SUG. I changed this setting to the last year and as expected there were lots of updates and the SUG was created. This gives rise to a few more questions: 1. The "Last 1 day" selection in the guide captures the updates released the prior day (Patch Tuesday) and creates a SUG for the new updates. I suppose that from the guide's stand point your system are currently all patched up to the date of implementing the ADR. My thought is that you have another means of capturing needed updates that are outside of the current monthly cycle. 2. What do you think about when creating the ADRs the first time you actually create the SUG for the past year to capture older updates and then change it to the recommended/desired date range? eg. Past week or month. 3. On this same step is there any pro or con to selecting "Superseded = NO?" It seems like that would weed out unneeded patches being downloaded. It's exciting when the light bulb goes on. I just might become a respectable SCCM admin if I keep this up.

I noticed that when I run (Run Now) the ADR everything seems to work fine but when I look under "Software Update Groups" I do not see that it was created. If it is not created will it prevent clients from downloading updates? Also it will prevent me from measuring compliance, right?

If anyone should run into the problem I ran into I follow the following to get the scripts to run. You will have to do it to both CM12Functions.ps1 and CreateFoldersAndCollections.ps1. 1. Save the script file on your computer. 2. Click Start, click My Computer, and locate the saved script file. 3. Right-click the script file, and then click Properties. 4. Click Unblock.

Sorry, I didn't mean to be a pain but yes I did read the guide. Your guides are very appreciated and have greatly accelerated our deployment. Here is my PowerShell window.

When I tried to execute the script I got the following error: File C:\temp\CreateFoldersAndCollections.ps1 cannot be loaded. The file C:\temp\CreateFoldersAndCollections.ps1 is not digitally signed. The script will not execute on the system. Please see "get-help about_signing" for more details.. Any suggestions?

Hi Peter, I just wanted followup and say thanks again for your help. I just migrated my first XP PC to Windows 7 while successfully maintaining the User State Data. I have another question with regard to Activation. I know that there is the option to "not" reset the activation. We are a Microsoft Enterprise Agreement organization. I want the newly upgraded machine to maintain its OS and Office 2010 activations so we don't have to reactivate them for each user. If I set the Task Sequence to not reset the activation will it give me the desired result and is the any drawbacks for this? Thanks, Paul

Hi Peter and thank. I guess I need to do some reading up on MDT. I don't know if I have access to it or not. As for deactivating the "Client Repair On Boot" option I am assuming that will be a "Run Command Line" step. Where should I insert that? After the "Setup Windows and Configuration" step? Thanks.

Hey guys, thanks for the help. Peter, after I delete the Apply Data Image 1 step and redeployed the TS everything worked. The first test VM was Vista and I will try XP today. Rocket Man, the reason I do not have any partitioning is that we want to preserve the exiting hard drive in case the user has data on it outside of their profile.

Hi Peter, I see you responded while I was composing the above. Using the Wizard I do not recall being given choice was to what would be installed where. I expected that SCCM would put the needed partition/volumes in the right spot. I guess I need to know what the Data Image 1 is. I am thinking it may be the hidden Win 7 boot partition but I don't know. If not then maybe it can be deleted. Oh, I told the sequence to keep the user state on the hard disk so it would not be sent to the server (to save bandwidth and speed). That might be what this is.