Scripting: Changing Networking Setup on Remote Windows Servers

I recently did a rather big reorganization of my domain controllers, in relation to an domain wide upgrade to 2008 server, and as a I result of this I had to re-configure the DNS settings for all my member servers. Being somewhat lazy and not particularly fond of repetitive tasks, I figured there had be a way to automatically change the required settings.


I ended up using a couple of great tools and some vbscript "magic" and was able to change the DNS settings on all my member servers within a couple of minutes.It would have been much more time consuming having to do this server by server manually, and this process also guarantees that the settings are the same on all my servers.

Enough with the rationale already, let's get into the solution itself. It's pretty easy, but does require a couple of easily available tools, a bat file and a VBscript.

Tools:

  • psexec
  • psexec @servernames.txt -c -p administrator -u [password] SetDNS.bat
  • DumpServernames.vbs
    This dumps all the server names in a given OU into a text file
    Usage: cscript DumpServernames.vbs > servernames.txt
    Set colItems = GetObject _ ("LDAP://ou=Servers, ou=something, dc=something, dc=local") For Each objItem in colItems Wscript.Echo objItem.CN Next
  • SetDNS.bat
    netsh interface ip delete dns "Local Area Connection" all netsh interface ip add dns "Local Area Connection" [IP DNS SERVER] netsh interface ip add dns "Local Area Connection" [IP DNS SERVER] index=2 ipconfig /all

Caveat alerts:

  • The netsh command outlined requires that the network connection you want to change settings on is called "Local Area Network".

    If you have manually renamed your network connections inside Windows 2003/2008, this will fail, so update the script accordingly


  • You will need to update the vbscript with your local OU setup as well as edit SetDNS.bat and insert your own DNS server IP values


September 11, 2009 at 12:17pm | 0 Comments
Tagged: , , , , , and

Lenovo Rethinks and Brings ThinkVantage System Update (TVSU) back

Lenovo has turned 180° and brought ThinkVantage System Update (TVSU) back from the dead. In a blog post on "Inside the Box" called "ThinkVantage System Update Returns", Matt Kohut, Global Lenovo Strategist, announces that System Update has been revived.


He goes on to explain that customer reactions, both blog posts and forum postings, has had such a big impact that it has caused Lenovo to rethink their decision.

Following our announcement, however, we heard from many customers on our blogs and forums. We’ve heard clearly that our individual and business customers alike value TVSU highly. Therefore, we are adjusting course based on your feedback, and have released a new version of TVSU on May 31st. In addition, we have made some backend investments which should indeed improve system performance.

As I posted about this issue a little while back, outlining my reaction to the discontinuation, I'm very happy to see that this gets reversed. TVSU is a valuable tool, and hopefully will continue to be so in the future.

At least it does seem like the downloads go a lot quicker now than before, but I fear that might just be temporary until "everyone" starts using TVSU again. I hope the investments Lenovo has put into the backend of things work out, also in the long run.


Re-reading my previous critical post about this, I realize that I probably was a bit ambiguous with regards to how we use TVSU in my organization though. We only use TVSU on the computers that doesn't get their updates from our own local repository that gets it's updates through the ThinkVantage Update Retriever (TVUR), and this has worked as expected through the period when TVSU wasn't available.

.

June 3, 2009 at 10:39pm | 0 Comments
Tagged: , , , , , , and

Lenovo Discontinues ThinkVantage System Update (TVSU)

A while ago, Lenovo pulled the plug on the old ThinkVantage System Update (TVSU) infrastructure and announed that they would return in the beginning of May with a new and improved system. While I am all for improvement and progress, I questioned why Lenovo had to completely remove the old (somewhat) working driver repository before the "new and improved" system was in place. I was willing to live with that, as long as we got a new and improved system in place. I was, in fact, looking forward to see what Lenovo was up to.


Today, I was pointed to this little gem on the Lenovo site

Lenovo is changing the way customers obtain updates for their PCs and Servers.

  • For our PC customers, automatic updates via ThinkVantage System Update (TVSU) are being discontinued. Customers can continue to download updates by accessing the Lenovo support site at Lenovo Support & downloads. Lenovo is pursuing alternative solutions for system updates and future offerings will be communicated through the new Lenovo Message Center Plus.

I'm sorry Lenovo, but completely discontinuing TVSU is not "changing the way customers obtain updates", it's telling your users that you don't value their time. Sadly, this is not the first time I've had that experience with Lenovo. I know this is pretty harsh, but consider the following scenario:

  • You run an IT-department when you standardize on Lenovo Thinkpads for your mobile workforce.
  • As a consequence of your standardization efforts you set up several deployment methods for these Thinkpads
  • Seeing that your preferred vendor provides you with tools like ThinkVantage® ImageUltra™ Builder, and ThinkVantage® System Update you decide to spend considerable time investigating and perfecting your deployment methods based on these vendor supplied tools that actually adds value to your hardware investments. It's kind of magic, but it works!
  • Lenovo then pulls the rug from under your feet and you basically have to start over.

This is the scenario I'm currently facing. Newer Thinkpad models, like the t400 and t500, are (naturally) not supported by the aging ThinkVantage® ImageUltra™ Builder (The readme for the trial download was last updated in 2007). Since we use it for deploying our base business OS and a minimal set of drivers this was a problem for us. After investigating a bit, we decided to try and give Lenovo a call and see if someone could help us out getting it to work on newer models.

I still can't believe how incredibly difficult it as to get support for that particular piece of software. Calling Lenovo support was useless, they didn't even know what product we were talking about. To this date, we have been unable to contact anyone in Lenovo, or IBM for that matter, that can help us with technical issues with it. No one. None. Zero! We did manage to get the basic drivers working inside the deployment image we have after quite a bit of investigation and trial and error on our own, no thanks to Lenovo.

So, where does ThinkVantage® System Update enter the picture? Well, we followed best practices and setup a minimal image that basically only includes networking drivers for the Thinkpad models we have. Then, and here's the magic part, the image installed ThinkVantage® System Update that connected to a local copy of the TVSU that contained the drivers we need for the rest of the devices. In reality, it's brilliant. Or, I should say that it was brilliant.

Now that Lenovo has yanked the foundation for our ImageUltra based installation services away from us, and we don't get support for it in the first place, what are we supposed to do? Manually download drivers and place it in the repository and hope the old TVSU client will find them?

Lenovo, I'm sorry, but this was not what you were supposed to be doing when you were "improving" the service. I've been a strong advocate for TVSU for a few years, even used it as a selling point when our business invests in hardware. Your most recent move has left me stranded, and now I need to start over setting up a distribution mechanism all over again. I know there are good alternatives to ImageUltra and, trust me, I know it has weaknesses, but I was willing to live with them as long as TVSU did the grunt work with regards to drivers. Right now Windows Deployment Services springs to mind, but that still leaves the problem with driver installation and management. TVSU sorted out that bit for us, and I'm sure Lenovo has other customers with similar stories.


I would really like to see the reasoning behind this decision, it sure doesn't make sense to me. But then again, I'm just a lowly user that actually utilized the very system Lenovo made available to me. How incredibly stupid of me.

Update 03. June 2009

: Lenovo reverses decision discontinue TVSU. Good one, Lenovo!

May 4, 2009 at 11:56pm | 15 Comments
Tagged: , , , , , , and

Lenovo System Update 3.0 Language Override

For some time, I've been having some issues with how Lenovo System Update uses the computers Regional Settings to determine which language it should use when installing drivers and software.

It turns out that there is indeed a way to override the automatic language selection, without having to resort to changing your Windows Regional Settings.

While reading through deployment documents for Active Directory integrated System Update, I found this little gem:


[HKEY_LOCAL_MACHINE\SOFTWARE\Lenovo\System Update]
"LanguageOverride"="EN"

That registry setting sets a language override that System Update checks before it determines which language to use. If the registry key is not present, or has invalid data in it, System Update does it's normal auto detection.

Valid two- and three- letter language codes are the following:

  • DA (Danish)
  • NL (Dutch)
  • EN (English)
  • FI (Finnish)
  • FR (French)
  • DE (German)
  • IT (Italian)
  • JP (Japanese)
  • KO (Korean)
  • NO (Norwegian)
  • PT (Portuguese)
  • ES (Spanish)
  • SV (Swedish)
  • CHS (Simplified Chinese)
  • CHT (Traditional Chinese)

Finally an easy way to override the language selector, and prevent Lenovo from "polluting" your computer with localized software you don't want.

May 21, 2007 at 11:07am | 4 Comments
Tagged: , , , , , , and

VMware VirtualCenter for VMware Server

VMware has announced the availability of a new version of VirtualCenter, specifically designed to manage VMware Server. This enables SMB customers to manage several instances of Virtual Server from one single console, and set up alerts based on CPU utilization etc. These features were only available for the enterprise VI3 customers until now.

VMware VirtualCenter for VMware Server is designed and licensed for use exclusively with VMware Server. The new virtualization management bundle, which includes one VirtualCenter management server for VMware Server with three agents and enterprise-class support including unlimited 30-day support from VMware, has a VMware list price of $1,500 and is expected to be available this week from VMware and VMware resellers. Additional agents can be purchased for a VMware list price of $400 per physical server managed.

Read the details in the Press Release

February 6, 2007 at 9:30am | 0 Comments
Tagged: , , , , and

 1 2 Next →