Nice list to share:
Source: Troy Clavell
Nice list to share:
Source: Troy Clavell
After installing Citrix Webinterface 5.1 on my Windows 2003 R2 SP2 64-bit VM i get the following error:
ISAPI Filter ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
To resolve this error you must prepare your IIS and ASP.NET 2.0 to an 64-bit application.
To run the 64-bit version of ASP.NET 2.0, follow these steps:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Enable32bitAppOnWin64 : (BOOLEAN) False
Finished installing ASP.NET (2.0.50727).
And my Citrix Webinterface is working:
By re-installing Client Access Role (CAS) on my Windows 2003 R2 Enterprise 64 bit and Exchange 2007 Enterprise machine I get:
“The Microsoft Internet Information Service is in 32-bit mode and this is a 64-bit computer. The mode must be changed before Setup can continue”
Today i had to install Windows 2003 R2 + SP2
I noticed that the installer just kept on going forever at the “installing devices” part.
Press Shit-F11 during setup to see what the Windows setup is doing. In this case the ‘add new hardware’ wizard was running. You can also use SHIFT-F10 to get a command prompt
1) Reset the virtual machine (don’t boot from CD-Rom)
2) Keep the focus within the virtual machine (don’t CRTR-ALT)
You’ll see it works this time, probably has something to do with the detection of keyboard and/or mouse.
Source: Peter Wigleven
In Windows Server 2003 Access Based Enumeration was a separate download you hade to download and install on your server to enable this option. For those of you who do not know ABE let me explain very briefly what ABE does.
Access-based Enumeration (ABE) has been included in Microsoft® Windows Server™ 2003 Service Pack 1 to a) increase folder level security, b) improve administrator productivity by reliably streamlining large directory structures for less-technically savvy users, and c) provide a more seamless migration experience for end-users migrating to Windows servers. ABE filters shared folders visible to a user based on that individual user’s access rights, preventing the display of folders or other shared resources that the user does not have rights to access. ABE can be accessed via graphical user interface (GUI), command-line executable tool, and a robust advanced programming interface (API).
Check out the details for Windows Server 2003 ABE: http://www.microsoft.com/windowsserver2003/techinfo/overview/abe.mspx
The good news is ABE is integrated in Windows Server 2008 and it has an GUI. Let me explain to you how to do it:
Het kan wel eens voorkomen dat een server spontaan een zwart scherm geeft op de console of tijdens een RDP sessie. Enkel is dit op te lossen met een herstart van de server, soms ook niet. Het is vaak gokken waar het gebruikersnaam, wachtwoord en domain moet invullen. Zie voorbeeld:
The Microsoft Windows Server 2003 Windows Time service, also known as W32Time, synchronizes the date and time for all computers running on a Windows Server 2003 network. Time synchronization is critical for the proper operation of many Windows services and line-of-business applications. The Windows Time service uses the Network Time Protocol (NTP) to synchronize computer clocks on the network so that an accurate clock value, or time stamp, can be assigned to network validation and resource access requests. The service integrates NTP and time providers, making it a reliable and scalable time service for enterprise administrators.
A domain controller that is configured to be a reliable time source is identified as the root of the Windows Time service. The root of the Windows Time service is the authoritative server for the domain and typically is configured to retrieve time from an external NTP server or hardware device. A time server can be configured as a reliable time source to optimize how time is transferred throughout the domain hierarchy. If a domain controller is configured to be a reliable time source, the Net Logon service announces that domain controller as a reliable time source when it logs on to the network. When other domain controllers look for a time source to synchronize with, they select a reliable source first, if one is available.
If the computers belong to an Active Directory domain, the Windows Time service configures itself automatically by using the Windows Time service that is available on domain controllers. The Windows Time service configures a domain controller in its domain as a reliable time source and synchronizes itself periodically with this source.
This describes how to synchronize the authoritative time server in a Windows Server 2003-based Active Directory by configuring the Windows Time Service.
How to configure Windows Time Service
1.Go to Start -> Programs -> Administrative Tools -> Group Policy Management
2.Locate the “Domain Controllers” OU
3.And edit the “Default Domain Controllers Policy” policy
4.Go to Computer Configuration -> Administrative Templates -> System -> Windows Time Service -> Time Providers
5.Edit the “Enable Windows NTP Client” policy
7.Edit the “Configure Windows NTP Client” policy
9.Fill in the “NtpServer” “nl.pool.ntp.org,0×1” find her the appropriate pool for your country
10.Select Type “NTP”
11.Edit the “Configure Windows NTP Client” policy
Your ready configuring the Windows Time Service gpo property. They policy will be applied to the domain controllers but this will take some time so we are going to force the gpo update on the domein controler.
1. Login on your domain controller
2. Go to Start –> Run
3. Start “CMD”
You can check if the policy has been applied by using the "Group Policy Management” tool.
1. Go to Start -> Programs -> Administrative Tools -> Group Policy Management
9.Select the tab "Settings" in the right pane
10.Click "Administrative Templates"
We checked if the setting are applied to the domain controller. The last step is to restart the “w32time” service.
1. Go to Start –> Run
2. Start “CMD”
4. Execute the command "Net start w32time"
The final check will be to open the “Event Viewer” and find in the system events the “w32time” event
1. Go to Start –> Run
2. Start "eventvwr"
3. Select "System"
4. Open the "w32time" event