/build/static/layout/Breadcrumb_cap_w.png

K2000 getcomputername.vbs does not work on scripted installs

We are trying to configure some scripted installs for some one-off deployments. 

We are trying to use this to pop a dialog box for us to enter the system name, but it never fires. 

"cscript GetComputerName.vbs /dialog /timeout:30 "

In the task list during the deployment it shows successful, but we never saw a dialog box to be able to enter the system name. 

Any ideas? 

1 Comment   [ + ] Show comment
  • If you run through your scripted install manually you may be able to find out what is happening. - nlieschke 9 years ago

Answers (5)

Posted by: SMal.tmcc 9 years ago
Red Belt
1
On your scripted install edit the setup configuration and remove <ComputerName>*</ComputerName>.  If you do not list that in the answer file and you DO NOT use the get set computer name scripts it will ask for a name every time.  If you want to keep the name of the computer you are imaging just put the get set commands in the deployment
Posted by: cserrins 9 years ago
Red Belt
1
There are several issues here.  One you are mistaking the built in collect/apply computername tasks (which are vbscripts), with the get/set computername scripts (which are .exes) and located at http://www.itninja.com/blog/view/get-set-computername.

Collect computername.vbs does not support scripted installs, not does it support an commandline switches.

Corey
Lead T3 Enterprise Solutions Consultant, K2000
Posted by: shanksr 9 years ago
Senior White Belt
0
We have that working at my school.  We use the .exe version as Preinstall Task and then do the SetComputerName.exe as a Postinstall Task.

GetComputerName_x64.exe /dialog /timeout:600
Posted by: dedenker 9 years ago
3rd Degree Black Belt
0
Script executed under a different user?
Posted by: EdT 9 years ago
Red Belt
-1
Is this under WIndows 7 ?  If so, you will never see a dialog box pop up when running under the system account, as Windows 7 now runs users in a different session to the system.  You can try enabling "interact with desktop" but this will always pop up the UAC prompt as interaction with desktop is considered a security risk and is no longer supported in Win 7 and 8.

Comments:
  • This is run during a scripted install of windows 7. It's during the preinstall before windows even starts. - roy.urick@koorsen.com 9 years ago

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ