Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by IcemanND

  1. ..... objSelection.TypeParagraph() if strFax <> "" then objSelection.TypeText "Direct Fax: " & strFax End If Set objSelection = objDoc.Range() ......
  2. http://www.microsoft.com/downloads/en/details.aspx?familyid=673A1019-8E3E-4BE0-AC31-70DD21B5AFA7&displaylang=en
  3. As vishyc88 mentioned CMDOW will work to hide the window, I created a AutoIt script that is launched from startnet.cmd and when it launches it hides the CMD window.
  4. I'm in the wrong business. If I had $600 for every image I built I could have retired before I turned 30. If you have a machine you can get it to boot on you could update drivers and re-sysprep the machine and capture a new image yourself. If you can get the BSOD it may make it easier to determine what needs to be updated, if the option on the boot menu is there to disable the reboot do that also. You could be dealing with chipst, mass storage and or processor (HAL) incompatibilities.
  5. I don't use gimagex but from what I remember it does not do anything other than give you a GUI front end to run imagex. I capture all of my images manually using imagex and deploy them with my own custom imagex frontend and have no issues.
  6. Reset the BIOS to defaults on the failing machine and see if it works.
  7. depends on the hardware configuration of the machines in question. If they are the same manufacturer and base model it will work fine. And even if they are different manufacturers and models if they are form the same generation of machines it will work 90% of the time. The problems arise when you start imaging machines that are newer or older than your base system model. In my case instead of throwing my time and headaches at it we purchased the Universal Imaging Utility which adds drivers to the image and handles the HAL swapping. It is made by the same company that originally created Ghost, Binary Research. I was tasked with making a single image that could be deploying to a 6 years span of XP compatible hardware on top of the rest of my duties. BTW Windows 7 has greatly simplified this process, no more HAL issues and so far I have not run into any MSD issues though I know some people have but all of the hardware I support have Intel chipset and mass storage controllers.
  8. Are you trying to make an image you can deploy to multiple systems? Or is this a I want to move everything from old machine A to newer machine B?
  9. The two most common BSOD when deploying an XP image to a machine especially when deploying to hardware that is different from the master system are 0x0000007B, which is a missing mass storage controller driver you can fix this if you add the hard disk controller drivers in the [sysprepMassStorage]section of the sysprep.inf file. The other is an incompatible HAL on the target system. Don't recall the BSOD code on this one since I have not seen it in a very long time. Windows XP installs one of seven different HALs on a machine, of those seven there are two pairs of them that Microsoft supports changing between, there are scripts online that let you switch between more of them. In my experience if you build you machine on a machine that is an Uniprocessor ACPI HAL when you drop it to a machine that would use a multiprocessor ACPI HAL it upgrades on its own. There was a period of time when the Intel Chipset and BIOS manufacturers conspired against me and this did not work.
  10. If you are deploying WIn7 I would recommend using WinPE 3. Something that might be related to your time issue may be drivers you have added to the boot image. Are you adding drivers, i.e. network interface drivers to the boot image? If you don't add them does it boot faster?
  11. Grr. Sorry about that. Looked fine when I hit submit, didn't look at it after that.
  12. strComputer = inputbox("Type a computer name","Enter computer name") if strComputer = "" then strComputer = "." On Error Resume Next Const wbemFlagReturnImmediately = &h10 Const wbemFlagForwardOnly = &h20 WScript.Echo WScript.Echo "==========================================" WScript.Echo "Computer: " & strComputer WScript.Echo "==========================================" Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2") Set colItems = objWMIService.ExecQuery("SELECT * FROM " _ & "Win32_ComputerSystem", "WQL", wbemFlagReturnImmediately _ + wbemFlagForwardOnly) For Each objItem In colItems WScript.Echo "Manufacturer: " & objItem.Manufacturer WScript.Echo "Model: " & objItem.Model Next
  13. What exactly are you trying to do? Keep a machine in a known state? If so it might be easier to use something like DeepFreeze or Clean Slate to keep the machines that way. If you are pushing out a new (changed) image that often I would look at something that you can manage the changes to the machines through like SCCM.
  14. I would think you should be able to copy the contents of the ISOs to a USB device. You will have to replicate the booting environment form the CD/ISO to the usb device. Shouldn't be too difficult.
  15. That is more or less what I meant. That the user account being used had the appropriate domain rights to join a machine to the domain in the computers OU. Essentially can you manually use that account to join a machine is the easiest way to check that. Easier way to test your images, build them in a VM. Dpending upon what VM software you use (my preference is VMWAre Workstation) you have the ability to take snapshots. Then whenyou need to test something you can take a snapshot before hand (take 30ish seconds) test what you need and if it didn't work go back to the snapshot (takes 60ish seconds) and try again. Has saved me many hours when building images.
  16. And the domain user and password used to join are valid on the domain to join a machine to the computers OU.
  17. Create a Windows PE cd/dvd/usb with the WIndows 7 setup files and don't add any commands to startnet.cmd, then you can run any commands you need and when you need to install windows run setup.exe form the windows 7 setup files.
  18. For the user issue you need to add a user account or domain account to the administrators group. I add a domain users group for the support personnel that support the machines. For the issue with joining the OU try specifying the machine object OU. Here is what I use in my answer file: <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserAccounts> <DomainAccounts> <DomainAccountList wcm:action="add"> <Domain>mydomain.com</Domain> <DomainAccount wcm:action="add"> <Group>Administrators</Group> <Name>Admin Members</Name> </DomainAccount> </DomainAccountList> </DomainAccounts> </UserAccounts> </component> </settings> <settings pass="specialize"> <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Identification> <Credentials> <Domain>mydomain.com</Domain> <Username>DomainAdmin</Username> <Password>DomainAdminPassword</Password> </Credentials> <JoinDomain>mydomain.com</JoinDomain> <MachineObjectOU>OU=computers,DC=mydomain,DC=com</MachineObjectOU> </Identification> </component> </settings>
  19. Try over at the autoit forums might already exist.
  20. But how can they make their backups when they have processors but no RAM?
  21. Reverse base 64 encoded starting at character 52. How about this: http://www.codeproject.com/KB/system/Product_Key_Finder.aspx
  22. Can't find mine, but here is a vbscript example.
  23. I posted the algorithm on the forum somewhere but can't find it at the moment. But the ProductKey is reverse base-64 encoded in the digitalproductid. Let me dig around a bit and I'll see if I can find it again.
  24. The problem you may run into is if you have a piece of software that uses the system pre-sysprepped SID and stores it in the registry or an INI file somewhere. Sysprep will not reset the stored SID when run and you will end up with duplicate SIDs with that application, SMS, SCCM, McAfee ePO, and TripWire are some that I know do this and I make sure to install after dropping an image.

  • Create New...