Jump to content

Recommended Posts

Posted

AS we have just got some new servers in, our boss has rejigged all the scripts from the lovely old batch files i could use, to VBS. Does anyone know of a site or guide i can use to learn this as i would like to be able to edit them myself without having to ask my boss every 10 seconds.

Thank you

Posted

All you need to do is open them in notepad, find where it points to the old server then change it to point to the new one.

 

Make sure you have configured everything on the new server first though.

 

Z

Posted
Theres also a couple on our wiki that you can play with/examine to see how they work (I believe from memory some even have indepth commented code for even more help.
Posted

yup! POWERSHELL :D

 

Also, depending on the scripts your using, make sure you go through the win2k8 GPO's Properly as there is alot more you can do using GPO rather than scripts! :) but yes look at powershell if i was you.

Posted
Also check out Script Center

 

You might want to ask your boss why he's using old fangled vbscript when he could be using nice, new shiny powershell (also at the technet script centre)

 

If I wanted a simple powershell script to msgbox the computer name I would open notepad put in the relevant code ( whatever that is ) and save it as what file extension and how would I run it and also what would the code be ?

Posted
When you open scripts in Notepad, you may wish to use the Edit > Replace function. Very simple to use and will make sure you find all 'SERVERNAME' entries.
Posted
When you open scripts in Notepad, you may wish to use the Edit > Replace function. Very simple to use and will make sure you find all 'SERVERNAME' entries.

 

I was thinking that but wanted to wait until the script(s) were posted so we could see the actual coding to see if they are using functions / subs or w/e

Posted
When you open scripts in Notepad, you may wish to use the Edit > Replace function. Very simple to use and will make sure you find all 'SERVERNAME' entries.

 

Don't think this is the problem - what @potato-peeler said is that the scripts have changed from batch files to vbscript so it's not just a case of what machine name to use but the whole language has changed!

Posted
Don't think this is the problem - what @potato-peeler said is that the scripts have changed from batch files to vbscript so it's not just a case of what machine name to use but the whole language has changed!

 

That as well @ language change from bat to vbs or powershell if they wanted to use powershell as per the above recomendation

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...