Sunday, October 20th, 2013
Today was a new message. I was supposed to convert two Linux servers to Windows 2008 Server. The two servers are HP DL360 G5s. Old but still usable as they were going to be workgroup servers.
The install procedure was to use the HP Smartstart CD.
One server converted without issue but the other after going through these two steps:
X:\windows\system32 > wpeinit
Gave the interesting error message of:
C:\hpssbem.exe is not a valid Win32 Application
Wait?……..This is a 64bit install?…….Why would it want a Win32 application?……..
I tried a restart. I tried to rerun the install and even formatted the disks but the same error occurred.
Finally, after clicking OK and using the console window; I had a look at the hpssbem.exe and found it’s size was “0.” Rather odd as why would there be a copy problem if it worked on the previous server?
I inserted the Smartstart CD again an located the application at:
I copied hpssbem.exe to C:\ and re-ran wpeinit which started the installation of the OS.
Thursday, July 25th, 2013
I was asked if there was a way to capture output of a specific program to a variable.
Basically, the person wanted to get a version number from the program.
Played around and had a way to accomplish this but I found a simpler approach.
$scriptOutput = & "c:\path\program.exe" -V 2&1
Obviously, the -V works with the program in question.
I am liking powershell
Thursday, July 25th, 2013
While scripting a report; I noticed a bogus error about a file version being wrong.
I examined the server in question and found the server service was not running.
I tried to start it but it stopped right away with the following message in the system event log.
The Server service terminated with the following error:
The account used is a computer account. Use your global user account or local user account to access this server.
Another server with the same problem would give this message:
Windows could not start the Server service on Local Computer Error: 1808: The account used is a computer account. Use your Global user account or local user account to access this server.
The service was configured correctly.
An odd problem and it’s cause was the fact a couple users placed URLs in the system Path variable (ie \\server\mount\dir).
Removing the entries and a reboot of the server corrected the issue.
Tuesday, July 9th, 2013
I was trying to debug a problem on a remote server through remote desktop.
I wanted to run a Windows File Protection scan (sfc) but was rewarded with:
You must be an administrator running a console session in order to use the sfc utility.
I looked at Microsoft and found this technote.
The resolution was was to run it locally as this was by design!!!!
I thought “Come on! I have to drive over to the machine!”
Then, I noticed “Applied To” and saw only Server 2000 listed.
What would happen if I started a command window as a local administrator (right click the menu option and select run as administrator)?
Lesson of the Day: Read the whole technote!
Monday, February 11th, 2013
I happen to notice this error would pop up on the application log every time a windows 2008 R2 server was booted:
Event filter with query “SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA “Win32_Processor” AND TargetInstance.LoadPercentage > 99″ could not be reactivated in namespace “//./root/CIMV2” because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
It didn’t seem to be bothering anything but why have an error if you can eliminate it. I did some checking around Microsoft and found this.
Normally, I like to review and run the script. I had other things to handle so I let the fix-it routine handle it. A quick reboot and there was no message logged.
Saturday, February 2nd, 2013
I have a script which uses psexec to check a few things on new servers. I ran the script and received the following message.
Couldn’t access *hosta*:
The handle is invalid.
Could not start PsExec service on *hosta*:
Access is denied.
Starting PsExec service on *hosta*…
Rather an odd message because another server with the same configuration didn’t have a problem. I checked a few things but did not find anything obvious. Server pings, remote desktop works, etc., etc…..
From the other box I tried to see if I could remote access the C drive via \\hosta\C$ and received this error:
Logon Failure: The target account name is incorrect
The AD account looked ok but when I checked the host; I found a typo. Instead of *hosta* there was *hosa* (obviously not the real name but you get the idea).
I deleted the domain account and simply renamed the server. The domain prompted for an admin level account to do this and rebooted.
Don’t forget to move the host to the proper AD group if you use them.
Moral of the story: DNS/AD is both a friend and enemy. DNS pointed to the correct server but simple things would not work while other things like remote desktop did. Well? Only because a previous problem prompted for a change in the negotiation level of RD.
It’s funny but I look back to my first AD design course and I remember the teacher repeating most AD problems are DNS related.
Saturday, February 2nd, 2013
I was setting up a new server and when it came time to test a few things; I received this nice message when I tried Remote Desktop:
The connection cannot be completed because the remote computer
that was reached is not the one you specified. This could be caused
by an outdated entry in the DNS cache. Try using the IP address of
the computer instead of the name.
I checked the cache and DNS and found it was in order. Remote desktop would work with the IP address.
This was one of two machines with the same setup and the configuration matched the other machine. I checked the Microsoft site and found this.
All you need to do is:
- Start > Administrative Tools > Remote Desktop Services > Remote Desktop Session Host Configuration.
- Look under Connections and Right-click the RDP listener (Connection name is RDP-Tcp) and select properties.
- Look in the security box where you should see the security layer is set to negotiate.
- Change it to RDP Security Layer via the drop down button.
- Click OK and close the Remote Desktop Session Host Configuration.
After that; Remote Desktop by hostname works.
I can’t explain why this happened on one of two identically configured systems. I could go back and hunt for a reason if I had time which I never do of course….
Well now. While working on another issue; I found the problem. The hostname was misspelled on the host. DNS and AD managed to give functionality but other things like simply mounting the C drive \\host\C$ failed giving the error “The target account name is incorrect” A quick delete of the domain record, a reboot and the problem is solved.
Friday, January 11th, 2013
Every major release of an OS brings changes to the layout. Such is the case of showing hidden folders on server 2008.
To enable hidden folder:
- Open the C drive and look to the left for the organize menu.
- Click it and select Folder and search options
- Click the View tab.
- Click the circle for Show hidden files, folders, and drives.
- Click OK
The hidden folders and files will now appear.