Category Archives: Windows Server

Troubleshooting FRS – SYSVOL Sync

Posted on by
1

A customer had a problem with synchronization between 2 domain controllers. Changes on the NETLOGON share on DC1 we’re not synchronized to DC2.

First thing to look for is events in the File Replication Service Event Log. On DC1 I did not find any events being logged but on DC2 I found a couple of warnings with eventid 13508:
The File Replication Service is having trouble enabling replication from DC1 to DC2 for c:\windows\sysvol\domain using the DNS name ad01gimd.directory.gimd.nl. FRS will keep retrying.……

So I restarted the File Replication Service on DC2. After the restart there was no warning anymore, just an informational message eventid 13516 stating:
The File Replication Service is no longer preventing the computer DC2 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL…….

I did the same service restart on DC1. This did produce a event Error with eventid 13568, stating:
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is   : "c:\windows\sysvol\domain"
Replica root volume is : "\\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons…….

To resolve this error execute the following steps, just make sure you’re not using a post Windows 2000 SP3 Operating System, as this solution is not recommended to  use on this OS:

  • open the registry editor and navigate to the key:
    HKLM\SYSTEM\CurrentControlSet\Services\NtFrs\Paramaters
  • Create a new DWORD value named: “Enable journal wrap automatic restore”  and give it a value of 1
  • restart your File Replication Service

This should produce a warning in your File Replication Service Event log (13560) stating:
The File Replication Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state,
Error status = FrsErrorSuccess
At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set….

So I gave the server 5 minutes. After that I got some informational messages in the event log (13553, 13554, 13516)

13553

The File Replication Service successfully added this computer to the following replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

13554

The File Replication Service successfully added the connections shown below to the replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
      "DC2.<Domain>"
      "DC2<Domain>"

13516 The File Replication Service is no longer preventing the computer DC1 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.

 

After creating a text file on one of the netlogon shares, it replicated correctly to the other domain controller.
Another problem solved, another happy customer :-D

IIS7.5: Application Warmup Manager

Posted on by
Reply

Now available for download: IIS Application Warm Up.

image IIS Application Warm-Up for IIS 7.5 enables IT Professionals to improve the responsiveness of their Web sites by loading the Web applications before the first request arrives. By proactively loading and initializing all the dependencies such as database connections, compilation of ASP.NET code, and loading of modules, IT Professionals can ensure their Web sites are responsive at all times even if their Web sites use a custom request pipeline or if the Application Pool is recycled.

Support change for Windows 200o and 2003 server

Posted on by
Reply

Original source: here

Windows 2000 Server

Extended Support for Windows 2000 Server will end on July 13, 2010. At this time, Windows 2000 Server will no longer be publicly supported.  You will be able to continue using "Self-Help Online Support"*

Windows Server 2003 and Windows Server 2003 R2

Also on July 13, 2010, Windows Server 2003 and Windows Server 2003 R2 (at a supported service pack level) will move from the Mainstream Support phase to the Extended Support phase.  During the Extended Support phase:

  • Microsoft will continue to provide security updates and paid support (Example: Premier and Essential support, per-incident telephone/web support, etc.)
  • Customers will continue to have access to all security updates and Self-Help Online Support options (Example: Knowledge Base articles, online product information etc.)
  • Non-security hotfixes developed during the Extended Support phase will be provided ONLY to customers who enroll in Extended Hotfix Support (EHS).

Please note: If you’d like to enroll in EHS, customers must already have a Premier Support contract. In addition, customers must enroll in EHS within the first 90 days of the Extended Support phase.  Program and per fix fees may also apply.  Customers with Software Assurance can enroll in EHS at any time.  

Service Pack 3 for Windows Server 2003

We have received inquiries from our customers and partners on whether or not there will be a need for a Service Pack 3 for Windows Server 2003.  Microsoft will not have a SP3 release for Windows Server 2003. 

To Summarize…

  • Self-Help Online Support* will be available for Windows 2000 Server after Extended Support before it ends on July 13, 2010.
  • Windows Server 2003 and Windows Server 2003 R2 will begin an extended support phase on July 13, 2010
  • There will be no Service Pack 3 for Windows Server 2003

*Self-Help Online Support is available throughout a product’s lifecycle and for a minimum of 12 months after the product reaches the end of its support. Microsoft online Knowledge Base articles, FAQs, troubleshooting tools, and other resources, are provided to help customers resolve common issues.

Where can I get more information?

GPP – Environment Variables

Posted on by
Reply

When you’re creating a Group Policy Preference, you can use Environment Variables. A cool thing is that when you press F3, a window will open which will display all kind of Environment Variables you can use.
Wanna give it a try?

  • Open Group Policy Management Editor
  • Browse to [User Configuration], [Preferences], [Windows Settings], [Folders]
  • Create a New Folder by right clicking in the Folders Section and choosing [New], [Folder]

    image 

  • The New Folder Properties Dialog will spawn

    image

  • Select the “Path:” Section and Press F3, the [Select a Variable] dialog will spawn

    image 

Now you can select your variable.

TIP: when you want to use variables which are user dependent. Use [User Configuration] instead of [Computer Configuration].

See Service Principal Names in your domain

Posted on by
Reply

To see all the service principal names registered in your domain, execute the following command:

ldifde -f <FileName> -s <DomainController> -t 3268 -d dc=forest,dc=root -r
"(objectclass=computer)" -l servicePrincipalname

this will return all computerobjects with an SPN and place it in the file <filename>. For all users execute the following:

ldifde -f <FileName> -s <DomainController> -t 3268 -d dc=forest,dc=root -r
"(objectclass=user)" -l servicePrincipalname

In this command replace forest with your NetBIOS domain name (i.e. marcvalk), root with your top level domain (i.e. net)