lord_hydrax

Well I figured it out..... I'd checked the box 'Do unattended installation of unsigned drivers on version of Windows where this is allowed' and apparently that was breaking it, because as soon as I unticked it the drivers worked fine. How that fixed it I've not a clue..... But I'm never ticking it again.

Thanks for the response. I do have the SATA Drivers injected into my WinPE image, however my build image has no drivers in it. (I like to keep it clean) Well I installed Windows 7 on it so I could see what the driver should be, sure enough it is the Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller. So I'll have to go over everything again and figure out why this one isn't working like any other HP...

Hello, HP recently released the Compaq 8200 Workstation which I am currently trying to add into my SCCM OSD Task Sequence for deploying Windows XP. The only thing I am having trouble with is the Mass Storage Drivers. I use an Apply Driver Package task with the 'Select eh mass storage driver...' option ticked and choose a AHCI Controller from there. (Using the latest Intel Rapid Storage Technology Driver) One website suggested 'Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller' which I couldn't get to work, I also tried the one from its predecessor the 8100 but that's not working either. When I say not work I mean I am getting the fun 0x0000007B Stop Error when the computer first leaves WinPE and tries to boot into Windows for the first time. Anyone happen to know what driver/controller to pick for this model? Thanks, Andrew.

....And fixed it. Despite Microsoft's format on their website being "A.U.S. Eastern Standard Time" I changed it to "AUS Eastern Standard Time" and now it is setting the timezone correctly. I was thinking it might have had something to do with those full stops!

I actually pulled off the error today from an SCCM report: Time Zone: A.U.S. Eastern Standard Time Searching time zone 'A.U.S. Eastern Standard Time' to find index. Setting product key. Setting local admin password. Licensing Mode: Per Seat Exiting with return code 0x00000000 Failed to find index value for timezone 'A.U.S. Eastern Standard Time'. Defaulting to GMT Standard Time Then I select one of our North American locations and its fine: Time Zone: Central Standard Time Searching time zone 'Central Standard Time' to find index. Index value for 'Central Standard Time' timezone is 20 Setting product key. Setting local admin password. Licensing Mode: Per Seat Exiting with return code 0x00000000 Same format of code for both...

Nope no good! Back to the drawing board....

I ran your command against my package from a command prompt and didn't get the errors you mentioned here. Might be an idea to try rebuilding the package unless you have access to that orca tool Peter33 mentions. What was the original command line you were running?

.....Definitely worth a try! I'll post back with how it goes as soon as I get a chance.

What I've essentially done is tried replacing "A.U.S. Central Standard Time" with "255" for the string. I've had no success myself using the index numbers, not sure if they are meant to work at all.

Thanks for the reply Lucid. The index numbers I referred to in my post are the numbers you mentioned there. I haven't come up with any other ideas at this point.

In my Program Command Line I specify the options, this is what I run for example: msiexec.exe /I "SEP.msi" ADDLOCAL=CORE,SAVMAIN /qn /l* C:\windows\system32\ccm\logs\sep.log Using that command I have had no problems installing SEP via a task sequence or software deployment. This however installs all the components, as specifed with the ADDLOCAL switch. You can get more info on this website: http://www.symantec.com/business/support/index?page=content&id=TECH102668&locale=en_US

Hey Guys, Might be a stretch but wondering if anyone here had any ideas.... I have a frontend hta built configured in the OSD Task Sequence which as part of it sets the variable OSDTimezone. I basically have a dropdown box with a list of locations available to set the timezone. My problem is that timezone names that have full stops don't set correctly and when the computer loads it has GMT time and not what was selected. I am using the microsoft list: http://technet.microsoft.com/en-us/library/cc772783%28WS.10%29.aspx An example is that if "New Zealand Standard Time" is selected it works fine however "A.U.S. Eastern Standard Time" does not. Here is an example of the vbscript section of the code: If sTSLocation = "Auck" Then oTaskSequence("OSDTimeZone") = "New Zealand Standard Time" window.Close() End If If sTSLocation = "Suns" Then oTaskSequence("OSDTimeZone") = "A.U.S. Eastern Standard Time" window.Close() End If I have had this working before but I'll be damned if I can remember now. I even put a msgbox in to ensure that it is picking up the rule correctly: If sTSLocation = "Dand" Then oTaskSequence("OSDTimeZone") = "A.U.S. Eastern Standard Time" msgbox "Dandenong Selected" window.Close() End If The msgbox displays however once the computer loads it is set to GMT time. I also tried using the index number but that does not seem to work at all. Any ideas? Is there some way I can check what the variable is set to during the build process as that might give me some clue as to what is going on?

Am I the only one that sees the OP replying to his own question then thanking himself in these 3 posts here.

Hello, I am having a problem with Notification Bubbles and was wondering if anyone had any ideas on how to fix it. Basically I advertise a package to our 400-500 computers and no one is recieving the pop up messages that are meant to appear in the system tray and take you to the Run Advertised Programs screen. I have configured the following settings in the the computer Client Agent Properties: And also these settings the interaction tab of the advertisement: This particular advertisement has a mandatory assignment 3 weeks after the actual date the advertisement started, so there should have been ample time for pop-ups to occur. It is not only users complaining that they have seen no pop-ups, but further testing myself shows that they are not coming up. I've spent a few hours on google trying to work this out with no success. Any ideas would be greatly appreciated! Regards, Andrew

Could be the setting under Advertised Programs Client Agent Properties. In the config manager console expand Site Management > SiteName > Site Settings > Client Agents and look at properties of Advertised Programs Client Agent. In this place there is a setting to have advertised programs appear in add/remove programs.

Hello, Having a bit of an issue with Clients at branch offices reporting back to the Primary Site Server. Here's the scenario, I'll try to keep it brief: We have a program advertised to our computers (delayed for a few more days) and it is set to only run on Windows XP sp3 computers. We have found the status of the Advertisement is 'Program rejected (wrong platform)' on a few computers with SP2 which we didn't realize we had, so we have gone an updated them either manually or using another SCCM package. These computers now show Service Pack 3 under System Properties and HKLM\Software\Micrsofot\Windows NT\CurrentVersion\CSDVersion where I am guessing SCCM grabs the information from. Computers at the same location as the Primary Site Server have since reflected this update in the database, however some computer at remote offices with either DPs or BDPs on site have not done so. The computers at the same site as the Primary Site Server can now receive/install the package but the remote office computers still show as rejected. I did some research and found the Hardware Inventory picks up OS service pack info, to which I ran this on the computers followed by a machine/user policy refresh but still they do not update. I also just ran every action on one computer in case that helped to no avail. Any idea what the problem could be? Maybe some logs I can look at or something? Appreciate the assistance. Regards, Andrew

Ha nice! I'll give it a try, does it work well?

Hello, Hopefully an easy one, I have deployed an Office 2010 package to several remote sites in preparation for an upcoming deployment. Today I added an additional file to the package source directory which is about 400kb and I want it to be replicated to all sites. Now for my question, if I do an Update Distribution Points task (Or refresh DPs task) will that replicate the entire package to all DPs or will it only copy the file that was added? Reason being, it took ages to copy like 3GB compared to what it would take to copy 400KB. If not, would it cause an issue if I manually copied the file to all DPs? Thanks in advance! Andrew.

Have to say I've been really enjoying IE9... But what does 'Run Away' do lol?

I believe Peter is on the right track for your initial issue, check how it resolved it for me: http://www.windows-noob.com/forums/index.php?/topic/3181-wds-and-sccm-pxe-booting-issue/ The way I see it WDS has its cache of info about the collections that it updates hourly and by making that reg change it resets every 2 minutes instead which is practically instant in most cases. I was on the same boat as you for months having to always restart WDS and while it didn't bother me hugely, what DID frustrate me was that my support guys had to constantly log on to my server and restart the service. As for the other issue, my first guess was DCHP was on the server but obviously that's not the case. I have definitely also had that issue before, I think it was the permissions to the RemoteInstall folder where your boot images are stored. Within this folder there is a folder called SMSIMAGES and I have added Users with read access to this. Probably situational a bit with the way I have my user accounts for SCCM setup and Authenticated Users might be more practical. Anyways maybe give that a try?

Actually I tried that a bit later after this post and that did actually work. Got the idea from a sysprep package I made from one of the guides on this site. Any idea whats the difference is between running a program from a package with Install Software versus using Run Command Line and specifying the package? I see no reason for it not to work either way! Its such a relief to get it the drivers installing but it would have be nice to have a consistant method to deploy them lol...

Hi, I am having absolutely no luck deploying Audio Drivers for any HP machines as part of OSD, specifically in our environment for the 6930p/8440p/6550b Notebooks and 7900/8000 desktops. I deploy other drivers with pretty much no issues using the 'Bad Driver' method by having them in a package running a setup.exe -s command to install. I try this with the Audio drivers and it never works. Though once the OSD completes and I log on for the first time, if I run the same silent install command it works just fine. I have tried running the command in Full OS and Win-PE mode, and also tried injecting using Apply Driver Package with no success. What are other people doing? Even if it is something I have already tried, at least I will have the right direction to be troubleshooting in. Appreciate the assistance! Regards, Andrew

This is something I've wanted for a long time too if anyone has any suggestions.

Nice one, that is exactly the sort of thing I thought it might be. I would assume this setting would need to be configured on each of our Site Servers that have the PSP Role. Thanks for the help!

Hello, I've been running OSD through SCCM 2007 for several months now (Thanks to the awesome guides on this site) and we constantly have issues with newly imported computers. Each time we import a new computer into SCCM we must restart the Windows Deployment Service so PXE booting picks it up. I only advertise Task Sequences to certain collections only. The normally process we go through is as follows: 1. Import the computer information providing a computer name and MAC Address 2. Update the collection membership and refresh it to check the computer comes up (I have a 'Deploy OS' collection I specifically created for the task) 3. Restart Windows Deployment Services on the SCCM Server If I try PXE booting the computer between steps 2 and 3 I get a 'PXE Boot Aborted' message or similar - if I try after step 3 it is fine. Same deal at my remote sites, you add a computer on the primary Site Server then you need to restart WDS on the local DP to the computer. This is pretty much guaranteed to happen ever time and is quite annoying, is there a checkbox I missed somewhere to 'auto-update' or something? Thanks guys! Regards, Andrew