Script Used to Work

Good Day
I have a script that was written by a former employee and it worked well running on a Windows 2003 server. After retiring the server and moving to a Windows 2008 R2 server, modifing the code to reflect the new drive letters and paths, the script refuses to run. The error message is a little cryptic and my normal routine of searching and troubleshooting has failed to turn up an obvious, at least to my feeble mind, answer on what else I have missed.
So I turn to the best place I know to get to the bottom of this.
Push-To-NBCVOD.vbs
Bob ConklinConfiguration/TEST TechnicianAsked:
Who is Participating?
 
Bob ConklinConnect With a Mentor Configuration/TEST TechnicianAuthor Commented:
Looks like I have hit a dead end, thank you for all your advice. The problem still exists so it looks like I will have to re-write the script in some other language that is a bit more friendly to a Windows 2008 R2 server.
0
 
Neil RussellTechnical Development LeadCommented:
How about you post the litle bit Cryptic error message :D Might help to give us a clue :D
0
 
Bob ConklinConfiguration/TEST TechnicianAuthor Commented:
After posting the original I realized that I forgot to attache the error mesage
VBS-Error.JPG
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Neil RussellTechnical Development LeadCommented:
This was a know issue with 2003 server and XP WMI queiries but have not heard of it on 2008.
There is/was a hotfix for both 2003 and XP, See http://support.microsoft.com/kb/828653

You may need to open an incident if nobody else has a suguestion here sorry.

UNLESS...

What is the target server you are registering the query against? What OS?
Maybe the hotfix needs aplying on that??
0
 
Bob ConklinConfiguration/TEST TechnicianAuthor Commented:
The target server is a Windows 2003 Standard Edition server, as I mentioned in my original post the script worked fine when the source server used was windows 2003. I can try to apply the fix to the target server if I can get approval to do that, we do not own that server.
Thank you for the insight though.
0
 
Neil RussellTechnical Development LeadCommented:
As the fix is a Microsoft Patch specifically for this exact issue I would hope that whoever owns the server has no issues with it. Its not like you asking to install a 3rd party product or anything.
0
 
Bob ConklinConfiguration/TEST TechnicianAuthor Commented:
Good Monday Morning
Recieved permission to apply the patches to the server, the server is/was running Server 2003 SP2 so the patch installer realized that the patches were/are already in place. I verified the file versions on the server are the same as posted in the KB article. The script still returns the same error message.

Thanks!
0
 
Bob ConklinConfiguration/TEST TechnicianAuthor Commented:
There was no further input or suggestions so it was prudent to close the question.
0
All Courses

From novice to tech pro — start learning today.