Wednesday, September 29, 2010

Run as Different User–Error–Service cannot be started.


Right click an app and chose run as option and provide correct credentials, following error occurs

“The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.”

To fix the above go to services, find Secondary Logon, change the startup type to manual.

Tuesday, September 28, 2010

Microsoft to drop Windows Live Spaces–Changing to WordPress as default blogging option

Microsoft and WordPress maker Automatic have announced that Microsoft will be ditching its Windows Live Spaces blogging technology in favor of using WordPress as the default blogging option for Windows Live. Considering the popularity of WordPress in the blogging scene…… read more from the source

Thursday, September 16, 2010

Reset trust relationship of a machine to the domain

Login as local administrator

use the following command

netdom resetpwd /Server:DCName /userd:domain\administrator /passwordd:*

Wednesday, September 15, 2010

Upgrade or Downgrade Aztech 600E Modem Firmware

It was not very easy to find the firmware so I am putting the URL online for anyone who needs it.

both upgrade and downgrade is easy, just follow the instructions in the package.

Outlook Calendar and Daylight Saving Time

Reoccurring appointments with wrong time

After you have made sure that all your exchange servers have applied correct time settings, clients (workstations) are in sync too and you have a few users complaining about time being incorrect in some of their reoccurring calendar appointments then considering the following may help. Outlook 2010 users may not be effected by this issue but if they are then the following link refers to a Time Zone Data Update Tool for it.

According to the following article Microsoft recommends to use Time Zone Data Update Tool for pre Outlook 2010 clients.

Here is the link to download 32bit tool for pre Outlook 2010 client

If you don't want to use the tool or if it doesn't fix the issue then manual edit of the appointment is required. This applies to reoccurring appointments.

Go to Outlook > Calendar and open the series of the reoccurring appointment which is not displaying time correctly.

Then click on reoccurrence button and here you will notice that the appointment time is displayed correctly. There are two ways to fix it.

  1. Remove reoccurrence save the appointment and apply it again
  2. Change the time zone to a different one and save the appointment then apply the correct time zone again and save the appointment.

Both of these options will generate updates and send it to all attendees, fixing the appointment time on their calendars are well.


Monday, September 13, 2010

Troubleshooting Daylight Saving Time Changes

It’s good to know a few facts before we go about troubleshooting DST changes.

By default the PDC in your domain becomes the Time Provider for the clients in a domain. So the first domain controller installed will become Stratum: 1 time provider.

If the PDC was decommissioned and role was transferred to a different DC then it would be necessary to run the following command on it to make it a Stratum: 1 time provide or a reliable time source for the domain.

w32tm /config /,0x9 /syncfromflags:manual /reliable:yes /update

Above command would make the DC or any member server you run it on a reliable time source for the workstations in a domain. Other DCs would automatically be Stratum:2 servers that means that they will get their time from PDC and will also be time source for workstations so they are client/servers.

For the DST changes to be applied correctly first make sure that all clients have all current windows updates installed by WSUS or directly from Microsoft. If there are still issues with some computers then see if following helps.

  1. Try to restart Windows Time Service

        net stop w32time && net start w32time

  1. If that doesn't fix it then consider the following:
  • Make sure that the clients are configured to get time from a the Domain

Run the following commands in the same order

         w32tm /config /syncfromflags:domhier /update

         net stop w32time && net start w32time

  • TimeZone related information is saved at three locations in registry


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

And the Time service parameters


"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones" is often updated by Microsoft and is applied through windows updates.

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time" has the configuration for the time service that includes where the machine should get its time from, whether this computer is a time server or a client/server or just a client and much more.

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation" when nothing works these settings do their magic when it comes to DST changes.

Problem Cases

  1. So you have already restarted the time service on a client and still it displays wrong time.
  1. Event log says that the client is getting time from the correct DC but still time is displayed wrong.
  1. You have setup the TYPE to NT5DS by running the command [w32tm /config /syncfromflags:domhier /update] which would force the clients to get the time from PDC but still it is displaying wrong time.


Find a computer that has correct DST applied - a computer that doesn't have problem

Go to the registry and export the following


And make sure to add the following entry at the end the exported reg file


This would make sure that the "Automatically adjust clock for daylight saving changes" is checked or enabled so you don't have the same issue.

The computer a txt file with the names of all computers that have problem and use the following command to apply changes (make sure to have pstools installed)

Psexec –s @txtfilewithcomputernames.txt regedit -s path\to\regfile.reg

Restart the computers

Hope it helps. Happy DST!!

Check the following for more info: