daniel.kuhn

Hi It has to be done silently

Hi You can start pqquery.exe /dsk[n] where n is the number of your disk. After that a few env vars are created...for example %D[n]SZ% holding the complete size of the disk... Or %D[n]UASZ% with the unallocated size of the disk. Then replace a placeholder value in the diskpart script file with a file manipulation tool or a vbscript. Afterwards start diskpart.exe with the option /s and the modfied script. If the last two partitions are of the same size you only have to specify the size of the firs partition....the last one can be created without a special size as diskpart will take the whole free space left on the disk....which should be the same as the previously created partition. Got it ? But pqquery is not freeware as it is part of the powerquest deploy toolkit Probably today it's better to write a short vb script. I think you can query the disk size in WMI... But when we did this before we were only dreaming about WMI support in PE

Hi I've a little problem. We stage our workstations by restoring a previously created sysprep image. We then copy a sysprep.inf file to the later os partition and perform a few modifications....like editing the later computer name according to an LDAP query (1:1 Link from MAC to Computername stored in an LDAP directory). This works all fine. After 2 reboots the workstation is automatically joined to the domain with it's new name etc... I now have the problem that I should modify a value of the later HKLM registry tree prior to the first reboot. So loading the later registry hive in PE, change the value and save it. Has everyone done this before ?

Hi As far as I know there is no support in diskpart.exe of specifying partition sizes in %. One way would be to start diskpart with a script. You could then create the script automatically and calculate the size of the last two partitions with a tool. Made this once with pqquery.... But I'm shure there are other tools out there or simply create a script doing this. What PE version are you using ?

Hi We had a similoiar problem in our domain. It was because our PDC emulator was receiveing time form a Unix based NTP server... We had to edit manually the following registry value: CompatibilityFlags Registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient Check the following link for more detailed information: http://technet2.microsoft.com/WindowsServe...3.mspx?mfr=true Sp1 has the following fix implemented that solved our problem an might solves yours as well http://support.microsoft.com/kb/830092/ Let me know if it worked...

Hi finally we made it work.... client is working client-server communication works fine restores are possible we only have one problem left to solve: as we're starting winPe directly from a RIS server, the win pe partition is different from the final system partition, meaning system state destination has to be changed. Unfortunately that doesn't work at the moment. Anyone has a solution for this ? target solution should be as follows: starting pe from ris server with systemroot z: restoring files to c: / d: / e: etc. restoring system state to c: instead of z:

cool....unfortunately we need it now and not when they are finished with looking into PE. I mean how long ago is it since MS has released the first verison of PE.....at least two and a half years What does Veritas takes so long to develop a simple restore application ? I mean we allready get the GUI running, registered the kernel drivers and the necessary COM components. It can't be so difficult to build code for a "stripped to the bone" Windows XP. The solution you talk about to be announced by Veritas in the future, is it a full client or a special kind of restore application like the BRM stuff ?

thanks for the info.... what's the meaning of NDA ???

Hi I started yesterday with a Veritas impkementation. As far as I know, Veritas is not directly supporting Netbackup clients on Windows PE. But we managed to get the GUI run, to install the three Kernel-drivers, and to register and start the server. But the client is not able to conntact the server. it seems as if the software has a problem with the socket initialisation. Is your installation running ?