Online Distraction
Jun 22nd
I’ve noticed my attention span dwindling over the last couple of years. I think this is mostly due to the amount of time I spend surfing the web, not to mention the amount of content (Facebook, Hulu, etc.) has been made available online at a rapidly expanding rate. What drains your attention the most?
[polldaddy poll=1726994]
(No Ratings Yet)
Loading ...NtFrs Error 13559 OR When in Doubt, Read the Error
May 20th
A customer was complaining that their “sysvol” share on their Windows Server 2003 R2 domain controllers was not replicating content (updated group policies, login scripts, etc.). Upon initial examination, I ran across this error in the event logs:
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13559
Date: 5/18/2009
Time: 6:53:52 AM
User: N/A
Computer: DC2
Description:
The File Replication Service has detected that the replica root path has changed from "c:\windows\sysvol\domain" to "c:\windows\sysvol\domain". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Changing the replica root path is a two step process which is triggered by the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
[1] At the first poll which will occur in 60 minutes this computer will be deleted from the replica set.
[2] At the poll following the deletion this computer will be re-added to the replica set with the new root path. This re-addition will trigger a full tree sync for the replica set. At the end of the sync all the files will be at the new location. The files may or may not be deleted from the old location depending on whether they are needed or not.
(No Ratings Yet) Loading ...Domain-wide Time Synchronization: A Personal Journey – Part 1
May 5th
Ok, this one’s been bugging me for a while. It’s one of those things that is not overly complicated, but just takes some time to dig in and get the process down right. Time synchronization is so important and necessary that we tend to take it for granted and never give it much thought. There are many problems and symptoms that can arise from systems that are out of sync. To the untrained eye, these problems can be difficult to diagnose and correct. But it all boils down to the fact that your Windows clients and servers should all be synchronized to an authoritative network time protocol (ntp) server, based on your Active Directory hierarchy. In a Microsoft Windows Active Directory domain, this is the domain controller that contains the PDC (Primary Domain Controller emulator) role. This system, in turn, should be synchronized with an accurate and dependable Internet NTP server or a physical device, like a GPS.
I am going to attempt to explain the steps required to configure time synchronization in a Microsoft Windows AD domain in the next few posts, but here’s a summary:
1 – configure NTP time source for PDC domain contoller
2 – configure poll interval on member servers (15 minutes; my preference)
3 – ensure that all member servers and workstations are configured for the NTP time source type of “NT5DS”
4 – test and verify time sync
(No Ratings Yet) Loading ...Using VMware Server 1.x to Break Exchange 2007 OWA
Mar 4th
Another dumb mistake: installed VMware Server 1.8 on an Exchange 2007 SP1 server with the client access role installed. Instead of choosing the “custom” install option, as I usually do, I was in a hurry and chose “complete”. Halfway through the install, I remembered why I never blindly choose “complete”; VMware Server Management Interface. VMSI is a web-based management interface for VMware Server that when installed changes the preferences for IIS by enabling 32-bit ASP on 64-bit Windows. This breaks OWA (64-bit ASP) because IIS 6.0 does not support running 32-bit mode and 64-bit mode at the same time on 64-bit Windows.
Here’s the fix:
Disable 32-bit mode
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Register 64-bit ASP
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Thanks to:
HOWTO: DIAGNOSE ONE CAUSE OF W3SVC FAILING TO START WITH WIN32 ERROR 193 ON 64BIT WINDOWS
(No Ratings Yet) Loading ...