Jump to content


Lucid

Moderators
  • Posts

    263
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Lucid

  1. I think that's all going to depend on how you deploy your software. For example, if you use Active Directory domain groups to control the deployments, then you could always script something to cruise through the current machine and then add the computer account object to the corresponding domain group - if that piece of software is already installed. Then after it's imaged, that software would flow back down (it might take a bit depending on your discovery times). Of course, there may be other methods, but like I said, it may depend on your particular environment...
  2. Have you tried packaging up the thing and installing it as software and not a Run Command Line item? And if you're having problems, then maybe post the code you're using in the .CMD file. Ususally the culprit is the path(s) being used in the script...
  3. We customize our deployments with a combination of settings in the "unattend.xml" file and a VBScript that runs at the tail end of our deployment process (copies files, sets registry key settings, that sort of stuff). As an illustration, our VBScript cracks open the default user registry hive and populates this registry key to show small icons on the taskbar: objWshShell.RegWrite "HKEY_USERS\CustomizeDefaultUserProfile\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced\TaskbarSmallIcons", "1","REG_DWORD" As for themes, we create a custom theme and copy that over as "oem.theme", but if you can't get Classic via the "unattend.xml" file, I think you can look at adjusting a registry key for this as well...
  4. That referenced hyperlink is for Vista and Server 2008. Just to make sure, did you follow the info in this one for Windows 7? In case you're just running into a syntax problem. http://technet.microsoft.com/en-us/library/dd744293(WS.10).aspx
  5. I'd just put the .VBS file in a folder, and then make that into a Package just like you would any other application. Then your Command Line is just the name of the .VBS file. And then you can add it into the TS just as if it were an application...
  6. You don't want to put any keys in your captured image - add those when you deploy the customized image to a machine...
  7. Does this answer your question? http://support.microsoft.com/kb/937251
  8. I don't think SCCM can do what you're wanting (hopefully someone can correct me if I've missed something). You want to install software on the machine, but hijack the user interface so nobody can log in. I don't think that's possible - although you aren't the only one that's wanted this ability in the past...
  9. Try calling the reg.exe utility with the /reg:64 switch to have it use the 64-bit verison. The SCCM client is a 32-bit application...
  10. I'd also suggest talking to those who control your GPOs and see if you can find an easy domain-based solution. If that doesn't work, if you can set those items via a registry key, then you could do it that way in your TS...
  11. What command switches are you using with SP1? Have you tried "/quiet /nodialog /norestart" (having the TS restart the machine)?
  12. Have you checked the Advanced tab of the Package's Program you are deploying to make sure you didn't check the box to supress notifications?
  13. Since I'm not sure where your other post is, I'll toss this out here... It sounds like either the Hardware Inventory scan hasn't run on that client and reported back to the SCCM server (start the Resource Explorer on the object and see what shows up for software), or you've got a hiccup in your collection query. If you want to post the query I'm sure someone could chime in...
  14. 1. Is the boot media generated from the exact same boot image listed in the Properties for the OS task sequence? 2. It depends on what you modify. I would suggest looking at the advertisement log for the TS before hitting the Apply/OK button because in some cases, yeah, it'll ruin the OS deployment and it has to be kicked off again for that machine.
  15. Lucid

    ACPI Hal problems

    Sounds like it's the HAL. You can either capture an image using a machine with the same HAL, or look into using a HAL replacement script... http://www.windows-noob.com/forums/index.php?/topic/574-geeks-guide-to-xp-hal-replacement/
  16. Just tossing this out there for whatever it's worth... One of the reasons it's recommended that the built-in "administrator" account be disabled is because everything has a SID, and the SID for that account is the same - so all the hackers and viruses already have half a foot in the door (http://support.microsoft.com/kb/243330). But yeah, many environments don't bother disabling it. It's up to you which way you go, but if a machine you imaged doesn't join the domain, then something errored out, so why would you try to log in and fix the machine? You can always use WinPE to boot up and pull log files. And some environments may rely on the TS instead of the .XML because they want one .XML file, but may require different local accounts to be created for various departments (FinanceAdmin, HRAdmin, TechAdmin, etc...).
  17. Just tossing this out there since nobody has chimed in.... 1. Have you checked to make sure you have the most up to date drivers? 2. Did you run the POWERCFG.EXE -DEVICEQUERY WAKE_ARMED command to make sure you had the correct spelling of the device? 3. Did you check to make sure your BIOS was up to date in case you're running into some odd bug?
  18. bbowen8 - if you haven't resolved this yet, and haven't already created your own post, you may want to do so with your specific details. Offhand, if there were no errors, but there's no .WIM file created, then it sounds like a driver issue, a security rights issue on the network space the file is being saved to, or a password issue in the TS...
  19. Have you double-checked your TS setting where you partition the drive? Are you doing a quick format using 100% of the drive?
  20. Have you checked out the info here: http://www.windows-noob.com/forums/index.php?/topic/1096-usmt-4/ ?
  21. You could certainly create some sort of wrapper script to be used, but what is it you're trying to do exactly? Are you trying to determine which of your AD machines does not yet have the SCCM client installed and running, and to push it out to them?
  22. One other thought you might want to consider... Can you just set your Package's Program to only install when nobody is logged in? I assume it won't be running then...
  23. Just tossing this out there since nobody has chimed in yet... Have you tried manually running things from a Command Prompt window to make sure you've got the needed command for your SCCM package? Typically I try to include the path to any transform or answer file when deploying an application - even when things say that you don't have to it helps prevent issues if there are multiple answers files and things like that... And if you're new to packaging Office, make sure you've checked this out: http://www.appdeploy.com/packages/detail.asp?id=1802 Oh, and if possible you might try editing the title of your post to "2010" instead of "2012" in case others are just skipping over it...
  24. I'm not sure if this would quite fit your problem, but... Why not let your collection do the work? Set up your collection to only populate if the application is not installed, or is a different version than the one you're currently pushing. Then limit that collection to another collection containing all the machines that would ever get the package (either your entire fleet, or a select group that you determine). Then set your advertisement to always rerun. A client gets the app, installs it, and then reports back in that it's installed, and the next time the collection membership query runs, it gets dropped from the collection. Some sample collection queries: http://myitforum.com/cs2/blogs/rbennett806/pages/collection-queries.aspx And if it quirks up, but remains installed, have another collection with a removal program targeted to it that you can plop the client into....
  25. Sorry, in the habit of explicitly specifying things since we typically have multiple MSTs for most things we do. So when in doubt, make sure to reference the specific file...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.