[How to set the time on a WinXP machine]

Here is the question.

I need to be able to set the correct time on my Windows xp machine before it joins the domain as if the time is out think its 5 mins it will not join the domain.

Now I have some PC's that the BIOS clock is not correct. so I can not use the Hardware clock to set the time.

I can set the time with w32tm but to do this I have to be in the domain first. I could use Netdom (2000 version) to set the time but this needs creditials and does not allways work.

So I thought about NTP my routers run NTP (Cisco) and I do not need to provide creditals.

How do I do a query /cmd line /program to query the NTP on the cisco and then update the windows os clock (Which I belive will also set the hardware clock UTC) thus will ebable me to join all my happy PC's to the domain.

And no I can not do it manually as I have over 12,000 or so to do :-(

[GImageX v2.0.1 Beta (ImageX GUI)]

Very nice,

As Geezery said a cmd line switch's would be nice.

How about deltas on images?

[I have 2 weeks to create a master image.]

lol

Unknown result? I know what the result it is all documented.

I work for the biggest IT contract currently alot of users more than 250,000 across more than 1000 sites.

the information I have provided is all the info I have received from this board :-).

I have one Image when I say image I mean I have one "Imagex Image" not really an Image its a bunch of files, this includes all my drivers for my current models.

I can deploy this by WDS, CD/DVD or USB it takes 3 mins on my slowest machine by USB. If I have any other models then I can inject the drivers into the "Image" I can do a SMS wipe and load if I want to. The user can rebuild his machine using WDS if he wishes everything is locked down.

Every last Detail is documented this includes the drivers used, I can hardly say download "The Driver packs" etc. Not that i am knocking the driverpacks by sneaky I can not use them in my Enterprise cause I can not truly say how it works.

I allready have a way of setting custom actions widescreens , DVD Writers, local printers, etc with the single build that I never have to update unless I have to go to a different windows version.

The question with hardware profiles is how can I script this? I could run an autoit script to manually send the keys but thats not our way.

I would go with the BDD way 2.5 or the 2007.

You can then decide if you want drivers in your image or out and let the BDD inject these depending on what you want, be warned there are loads of ways you can do this in the BDD. I will take more than two weeks to read and digest the thing!

BDD is free and supported which has to be in my case as I am not allowed to deploy anything that is not supported due to our "contract"

unknown result lol

TCO's depend on the size of the company if you have 2 Weeks to do a single image for less then 100 users then I would not bother with the BDD if you have more than 500 then the cost to invest time into the BDD will in the end lower the TCO.

[I have 2 weeks to create a master image.]

if the script your talking about is Johan's then......

Build your image on a machine that is a uni proc place all your drivers in your desried location.

Download spdrvscn.exe from www.vernalex.com

download...

pskill.exe

psloglist.exe

sync.exe

from sysinternals.

Place all these files in your sysprep folder.

use this batch file and adjust it to point to your driver folder..

rem Infrastructure Team
@ECHO OFF
CLS
ECHO System Preparation Tool
ECHO.
ECHO Before continuing please:
ECHO 1. Be sure that the pre-sysprep steps were followed.
ECHO 2. Image the computer previous to this, as the sysprep
ECHO process may fail and this would corrupt the installation
ECHO you have prepared.
ECHO 3. Restart the computer before attempting this so that
ECHO system buffers are cleared.
ECHO 4. Close all open windows before continuing.
ECHO.
pause

ECHO.
ECHO Flushing data to disks (preliminary):
sync -r -e

ECHO.
ECHO Cleaning up old driver caches:
del /s /q c:\drivers\infcache.1

ECHO.
ECHO Creating driver path (SysPrep Driver Scanner):
spdrvscn /p c:\drivers /e inf /d C:\windows\inf /a /s /q

ECHO.
ECHO Closing open SMB connections:
net use * /delete /yes

ECHO.
ECHO Terminating unneeded processes:
kill /f vptray
kill /f ccapp
kill /f explorer
kill /f alg
kill /f ati2evxx
kill /f ccevtmgr
kill /f ccsetmgr
kill /f defwatch
kill /f lucoms~1
kill /f mdm

ECHO.
ECHO Stopping unnessary services:
net stop alerter /yes
net stop wuauserv /yes
net stop browser /yes
net stop cryptsvc /yes
net stop dhcp /yes
net stop mdm /yes
net stop trkwks /yes
net stop protectedstorage /yes
net stop remoteregistry /yes
net stop seclogon /yes
net stop samss /yes
net stop wscsvc /yes
net stop lanmanagerserver /yes
net stop "symantec antivirus" /yes
net stop defwatch /yes
net stop ccevtmgr /yes
net stop sndsrvc /yes
net stop ccpwdsvc /yes
net stop ccsetmgr /yes
net stop sens /yes
net stop srservice /yes
net stop schedule /yes
net stop lmhosts /yes
net stop ups /yes
net stop uphclean /yes
net stop webclient /yes
net stop audiosrv /yes
net stop sharedaccess /yes
net stop msiserver /yes
net stop w32time /yes
net stop wzcsvc /yes
net stop lanmanworkstation /yes
net stop spooler /yes

ECHO.
ECHO Removing cached OEM drivers...
attrib -r -a -s -h C:\windows\inf\oem*.*
del /q c:\windows\inf\oem*.*
del /q c:\windows\inf\infcache.1

ECHO.
ECHO Clear the event logs...
psloglist -c application
psloglist -c security
psloglist -c system

ECHO.
ECHO Flushing data to disks (finalization):
sync -r -e

ECHO.
ECHO Executing system preparation tool (reseal / minisetup)...
start sysprep -reseal -mini -quiet -shutdown

Once your image is built go into device manager and then expand the computer icon, right click and then update the ACPI type click "Install from a list" option and then click "Don't search I will choose option" click "next" and then choose " Advanced Configuration and Power Interface (ACPI) PC"

Ok now for the sysprep.inf make the settings you require. Do not use the oempnpDriverspath spdrvscan will scann all dirs and then place this directly into the registry for windows to search for drivers paths.

Don't forget to add your mass storage Device Driver IDS into the sysprep.inf for the machine to boot.

If your running new hardware that has the new Sata drivers then use "IDE Merge" attachd to this post this will pre-stage the drivers into the windows registry so that when windows boots it will correctly install the correct Sata driver..

iaahci.inf or iastor.inf

Set up Windows 2003 with WDS with PXE for your winpe image to deploy to your clients (Do not forget that you need Drivers for the Mass Storage Device Drivers and network in the winpe image) now as Iceman said if your going with winpe 2.0 then you need at least 348mb of ram to create a pri a partition

The PXE server will answer requests for the "F12" send the winpe image to the client partition the drive lay an image from a share, look up the hal type "HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID" (winpe 2.0 and winpe 2005 use the same reg key to find hal type)

Run the ztihaldetect.vbs to adjust the sysprep to correctly which will adjust the sysprep depending on the hal IE: if it reports "Advanaced Power Interface ACPI PC" it will not do anything. if it reports "ACPIAPIC_MP" then it adds an entry to sysprep in the unattended part "UpdateHAL=ACPIAPIC_MP,%WINDIR%\Inf\Hal.inf this will then get its files that are required from the "dllcache" the machine will now have the correct hal.

If you would like the "IDE Merge" then please PM me (its 201k :-()

I have managed to reduce the companys images from 35 to 1 which includes laptops.

Only thing I need to work out is how to do laptop hardware profiles from the cmd line.

[psexec on WinpE2?]

what services are running?

[WINPE 2 AND THE HP SSSTK 1.8]

Hi,

I have downloaded the Smart Start Scripting Tool Kit Version 1.8 now all the tools work if run locally apart from the "cpqacuxe.exe" This tools is used to configure the RAID card.

I have built my UFD winpe 2 image with all the packages and Imagex.

I included all the drivers from the download in the imagex by using the peimg inf= command. I can see all my Disks and Networking is working fine (NC Multifuction Device :-))

When ever i run the "cpqacuxe.exe -s" to save my config i get the egg timer brielfy and then nothing.

Does anyone have this working?

I am running on a ML350 G5 with a e200i raid controller

[Broadcom multi function Driver]

Just to let everyone know..

I downloaded the HP Scripting Toolkit Version 1.8 and this now includes winpe 2 support.

There are extra drivers now for the multi function Nic broadcom driver.

I have not tested all the tools yet.

but its looking good.

[HP BL25P G2 server blade]

well your in luck cause the new HP Smart start scripting toolkit Version 1.8 has all the drivers for winpe 2 now which includes the multi fuction nic driver

[Winpe 2005 with w2k3 r2 source boot on UFD?]

got it all worked out now...

I have not bothered with the SDI boot into ram method etc..

I have formated my UFD's with the HP Format Utility and used pe2usb. to create and copy over the files to the UFD.

I placed my scripts in the system32 and copied over my wim image to the root of the UFD X:\Images.

Nowe when the engineers change the desktop hardware they then boot the UFD so that it does the following....

Formats the drive and sets the drive up how I want it

lays the wim onto the drive

It then pulls up a hta with the Computername and asset details which the engineer inputs.

this updates the sysprep.inf and updates a text file call bios.txt

I then write to the bios my boot order, password and asset tag details the machine reboots and then joins the domain.

whole process takes 5mins a machine which I am happy about.

Once all the machines have been done I will then have sms 2003 and ris to deploy my wims which can check the bios for serial and asser details mapped to its pc name.

[PE 2.0 Boot Screen]

sounds to me you have nearly done it.

How does the bootmgr.exe.mui get picked over the normal one?

[PE 2.0 Boot Screen]

Use the mui version to get round the checksum issue

[Winpe 2005 with w2k3 r2 source boot on UFD?]

Has anyone done a winpe 2005 image built with windows 2003 R2, created a SDI image and boot into Ram with a UFD?

Ok guys I want to make a UFD Bootable with a SDI image that only needs to have support for diskpart, vb script and cmd prompt

I would also like to have another partition on the UFD to hold some scripts and a wim Image.

Has anyone done anything like this before?

And No I dont want to use winpe 2.0 as I have a few machines that have 256mb of ram an even tho I can boot these machines with winpe 2.0 I can not create any pri partitions.

["Windows is loading files..." message needs to change.]

Well at the moment you cant as this file is protected. The file is a dll and I forgot the name of it I will look it up when I get a moment

However the mui version of the file is not protected. I have seen one place on the net that talks about chaning this I will dig the link out when I find it.

[Imagex GUI Open Source]

can you try and re create your problem in vmware and send me a screenshot?

[Imagex GUI Open Source]

Hi when your making your winpe image I would mount the boot.wim within sources and add the files there in system32 so that you do not have to do the full path for imagex.

The intclg.exe is in my windows aik\tools\x86\intclg.exe

This is just a wrapper dont forget the cmd will be displayed at the bottom of the gui if you cant run the cmd by the cmd then its not going to work in the gui

[Bart PE urgent help]

Well everything looks ok.

You said that it works ok with vmware ok?

Maybe its a Hal Problem or Mass Storage Device Driver.

What machine are you deploying too? can you run devcon on the "Tin"?

if you need guidane on how to do this then let us know I will keep an eye on this thread fro you

[winbom.ini disk config help.......plzzzzzz]

MMM I working just on the same thing I am not in the lab at the mo but I run a few tests.

Do you only have one winbom.ini?

As I beleive that there is a an order that its serached for IE:-Reg key, root of removable devices etc.

Please keep me informed if you do find the answer

[Bart PE urgent help]

Ok some more questions for you

Are you using a dhcp and tftp server on the same server?

You have all the dhcp settings set up? like option 67 and option 66?

Have you tried to install WDS/Ris then just copy your files to the template folder?

[How I can use vbscript in WinPE 2.0]

Its nothing silly like your disk is in th raw state?

Sometimes I forget to format my drive after diskpart and then do the the imagex /apply and get the error "file not found"

[Making an OS image]

Well you can use.....

wimbom.ini as described in the DOC's and format the drive.

Also you can mark the drive as active in wimbom.ini

You can then use OEMRunonce for imagex.exe

For your image I would read up on referencing drivers with sysprep and don't forget the HAL are all your computers compatiable?

But again this can be done easy enougth by sealing the machine as "ACPI" and then run a script to update the sysprep.inf this could be done in OEMRunonce as well.

Or you can use startnet.cmd and then call scripts from there.....

call diskpart and call imagex

As stated in the previous post I would defo read the DOC's winpe.chm

[deployed Office in Unmanged State now need to Install in Manged State]

Hi,

I have a number of Machines that Have Office 2003 Enterprise on which was installed as part of the build.

Now I also have an Intellimiror DFS share with a GPO and an Office 2003 AIP.

I would like to somehow try and change the machines with Office 2003 on already so that they thing they have been installed by the GPO so that when the GPO runs it does not re-install Office.

I know I could just un-install Office on the Machines that did not have the GPO Office but I have a 10mb network with 500 or machines on each site so thats no good for me.

Has anyone got any ideas or a way I can do this?

I thought about taking a reg snapshot of the office 2003 install with the build then let GPO re-install the Office 2003 AIP Version and take an after snapshot and compare the both.

[Unable to create Discovery Image]

Have you gone thru the whole WDS process?

I am wondering what the support is like for HP Kit etc.. I take it you still need a PC with at least 300MB of ram to create the primary partition?

[Bart PE urgent help]

A question for you.....

what is the amount of ram in the computer your trying to boot?

It looks like the RamDisk cant load properly try a Build without the ramdisk to troubleshoot first then step it up.

Don't you need to change the imagetype="Winpe" instead of "Flat" not sure been a long time since I installed TFTPD and then booted Bartspe. I have switched to winpe2005 SDI for customer support issue's

[WinPE via WDS extreamly slow]

I would look into splitting your wims into smaller chunks if WDS can hadle swn's that is I have not tested this yet.

[Imagex GUI Open Source]

Please see first post for edits