Thursday, April 27th, 2017
I have a secured cluster where there is no Net access. The users had licenses for Office 2013 and wanted to use them inside the cluster.
Office likes to activate itself. It tried and gave an error. I restarted Word and it gave the options for Internet and telephone activation. I selected telephone and I selected my location and was rewarded with:
Telephone activation is no longer supported for your product
Oooooookay. No Net and no telephone…….
Luckily this is just a “feature.”
I went through the telephone process and activated the installation. The only problem now are templates which appear to be downloaded from the Net. But, I will take care of that if they complain.
Friday, January 6th, 2017
One of our services gave an odd error. External user would attempt to access it and they would get an error about a configuration file not downloading.
The part of the error message that interested me was:
Failed to download this file. Error code 0x800C0008
What was odd was the service worked inside the firewall.
I thought it was browser related and checked the Net.
I tried the suggested registry change:
- Start Registry Editor.
- For a per-user setting, locate the following registry key:
For a per-computer setting, locate the following registry key:
- On the Edit menu, click Add Value, and then add the following value:
- Exit Registry Editor.
This did not need a reboot and the change worked.
To add more “oddness” the service started working before the affected users made the change.
Hmmmmmm? Network people or Security people?
Wednesday, June 18th, 2014
Cygwin is a *nix-like interface for windows. Like all applications, it has versions and sometimes that can be an issue.
There is the command:
But, there is a great deal of information so you would have to use grep to get what you need.
A quick and simple approach would be the old trusty “uname” command.
$ uname -srv
CYGWIN_NT-6.1-WOW64 1.8.3(0.237/5/3) 2011-03-30 12:12
$ uname -r
Now if only I could convince some people you don’t have to stay at a version forever. 😉
Wednesday, April 17th, 2013
Every once in awhile I come on a workstation which only has “Logoff” or “Disconnect” through remote desktop.
What to do when you want to reboot or shutdown?
There are a few ways to do this:
1) You can use the Alt+F4 keys to bring up a shutdown window which has the options for restart and shutdown.
2) You can use the Ctrl+Alt+End keys to bring up the old Ctrl+Alt+Del menu where you can select shutdown or restart
3) You can enter: shutdown -s -t 10 to shutdown in 10 seconds or you can enter: shutdown -r -t 10 to restart in 10 seconds.
Keep in mind new operating systems will do things different such as the Ctrl+Alt+Del menu is different for windows 7.
One thing I find still works is the shutdown command.
Finally, I keep forgetting the Alt-F4 approach. I was reminded of it here.
Friday, February 8th, 2013
Every once in awhile the question of what is the maximum memory for a windows operating system is raised. The 32 bit versions are easy but the 64 bit versions can have different sizes depending on the OS.
Microsoft does give a list.
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.
Sunday, December 30th, 2012
I was tasked with adding several machines to a network KVM switch. The HP servers run iLO for remote management functions and they easily installed. The DELL servers use DRAC which required work to get them configured. One DELL server didn’t have a DRAC card so I had to use IPMI.
The server ran Windows 2003 which does not automatically install the IPMI driver. This is accomplished through Add/Remove Programs.
- Click Start, Control Panel, Add/Remove Programs.
- Click Add/Remove Windows Components.
- From the component list, select Management and Monitoring Tools, and click Details.
- Select Hardware Management.
Wait a minute! Where is the Hardware Management option?
It turns out this option is only available with the R2 version of Server 2003. A quick installation and the option was available.
Following the same steps as above, the next step is to click “Next”
The installation wizard will start and it will ask for the Windows Server 2003 R2 installation disk.
After it’s installed; it would be a good idea to verify installation as there is a technote and a hot fix to install if the IPMI driver does not appear.
To verify installation:
- Click Start, Control Panel, System.
- Select the Hardware tab.
- Click Device Manager.
- Click View, Show Hidden Devices.
- Expand System devices.
Look for Microsoft Generic IPMI Compliant Device. If it exists, it’s installed. If not, enter the following command:
rundll32 ipmisetp.dll, AddTheDevice
The device should appear. If not, you might need this hotfix.
Once the device is in place, we can go about configuring it.
I will present this in another post.
As always; the useful links:
Monday, April 23rd, 2012
Every once in awhile I will get a question about what do the color buttons mean with MOC?
There presence buttons serve to tell you the availability status for MOC sessions. The common colors seen are red, green, yellow, green-yellow and redish-white(kind of a pink?).
Red – This means do not disturb. It is manually set or appears when a user is has a scheduled event in the outlook calendar.
Green – The user is available for chat.
Yellow – This means away or out of office. This can happen when a user sets it, the office assistant was set, or more often the computer was idle for 15 minutes.
Green-Yellow – The person might be available. This happens when the user’s system has been idle for five minutes (default).
White with Red hue – The person is not available. This can happen if the person configured it or communicator is not running.
These are the basics and I have found most people figure this out on their own. If a person want’s to read more about it, there is a Presence Survival Guide provided by Microsoft.
Monday, March 26th, 2012
I have a new server running windows 2003 R2 to support legacy software.
The server sits in a secured room which does not have access to the Internet. As such it was installed by DVD.
The operating system included service pack 2.
When it came time to configure NTP(we have an internal clock), the time would adjust one hour backwards.
I checked the the following:
- Time Zone. Correct
- Automatically adjust clock for daylight saving changes is checked. Correct
- The BIOS clock. Correct
- The time server is accessible. Correct.
- Patch levels. Possible problem.
I remembered the time when the government decided to extend daylight savings time and decided a patch was missing.
I searched the Microsoft site and found KB955839
I installed the patch and my time synchronization was correct.
Lesson of the day: Don’t assume the service pack has all needed patches.
Saturday, March 17th, 2012
There was a case were an LSF installation had to be reinstalled on a Windows 7 machine. We ran the uninstall and deleted the LSF folder from the C drive. However, when attempting the re-installation; we received a message about the LIM service already running for the cluster.
Checking the services; I found Platform LIM still listed. Normally you would also see Platform RES and Platform SBD.
The suggested solution was to re-install the system. This was not attractive as the build process takes time to configure and verify for production.
My first thought was the service was keeping the installation process from running. The question was how to remove it?
After a little search I found the sc command which allows you to use the command line to interact with the Service Control Manager and Services.
The command needed: sc delete [service name]
Now what would be the service name? If you return back to the services interface and double-click Platform LIM, you will see the service name which is : LIM.
You can also use the sc command by entering: sc query | more
This will list all services. Look for Platform LIM and above it will be the service name.
After I found the service name; I entered:
sc delete LIM
The service went away and the LSF installation was successful.
Technet Documentation for sc delete.