phreek.org

When starting MS Works for the first time under a new user profile, you receive the message “Cannot display the End User License Agreement which must be displayed and accepted before you can use this application. To display the agreement, reinstall the application.”

To fix it, I copied WKS6EULA.txt and st02eula.txt from my MS Works CD (D:\MSWORKS\COMMON\MSSHARED\WKSHARED\RETAIL) to “C:\Program Files\Common Files\Microsoft Shared\Works Shared”.

If you’re running a different version of works, your EULA file may be named either WKS5EULA.txt or WKS7EULA.txt as well as st03eula.txt so you will need to adjust accordingly.

• Download the IIS URL Rewriter module from Microsoft and install it on your IIS server.
• Open IIS Manager and in your site you will now have an icon for “URL Rewrite” so double-click it.
• In the top-right click “Add Rule(s)..”
• Select “Blank Rule” under “Inbound Rules” and click OK.
• Enter “Strip index.php” in the Rule Name text box.
• Enter “^(.*)$” into the pattern text box.
• Expand Conditions and add a rule each for “Is not a file” and “Is not a directory”
• Under Actions, in the Rewrite URL text box enter “index.php/{R:1}” and untick “Append query string”
• Click “Apply”
• Edit your CI system/application/config/config.php file and set $config[‘index_page’] = “”;

I ran into an issue while upgrading components in preparation for our XenApp 5 migration where after installing Web Interface 5.2 I could connect and see my published applications but when I tried to launch one I would get an error “Citrix online plug-in could not contact the server”.

The solution is to edit the WebInterface.conf in your PN Agent IIS site and add a line “RequireLaunchReference=off”.

It took quite a bit of Googling but I found the solution.

The reason for this problem is that MS KB953230 uses the same range of ports as WDS defaults to (64001-65000) for TFTP file transfers so you need to set WDS to use a different port range (62000-63000 works well). This will only occur on a server where you have the DNS role installed as well as WDS (most likely a domain controller).

You need to set “User Configuration \ Administrative Templates \ Windows Components \ Internet Explorer \ Turn Off Tabbed Browsing” to “Disabled”, then set “User Configuration \ Administrative Templates \ Windows Components \ Control Panel \ Display \ Desktop Themes \ Load a specific visual style or force Windows Classic” to “Enabled” but leave the path blank.

As we’re implementing a migration from Windows 2003/Exchange 2003 to Windows 2008/Exchange 2007 at work at the moment I’ve been doing a lot of reading on FSMO placement for the new domain controllers. I found this article which gives a clear outline of how it should be done.

In my environment, we have 1 physical DC which is also the file server and TS licensing server, and another VM which is built specifically as a DC. The VM is assigned the Schema Master, Domain Naming Master, PDC Emulator, RID Master roles and is a Global Catalogue, while the file server will handle the Infrastructure Master role and will NOT be a Global Catalogue. All DCs at branch offices will be setup as Read Only DCs and will be Global Catalogues and will be configured to cache the passwords of the users at that office. As we are also running Exchange 2007 at this site I am evaluating whether there is another server we can promote as a redundant Global Catalogue.

For this you’ll need an IIS 6.0 server with the web and SMTP components installed, as well as the IIS 6.0 Resource Kit Tools.

Install the SelfSSL component from the IIS 6.0 Resource Kit Tools.

Create a new web site in IIS and note it’s site ID by clicking on the “Web Sites” parent in the tree on the left and looking for the number under the “Identifier” column. Open the properties of your new site and set a port for SSL (I chose 442 to avoid conflicts with any pre-existing SSL sites)

Open Start -> Programs -> IIS Resource Kit -> SelfSSL and at the command prompt run (replacing variables to suit your environment):

selfssl /S:<site-ID> /V:3650 /N:CN=<hostname> /P:<site-ssl-port>

So for example I ran:

selfssl /S:87257621 /V:3650 /N:CN=SMTPGWY /P:442

You should make sure that the <hostname> is the same as that of the server on which you are running the SMTP virtual server.

Open your new site and export the certificate as a PFX file.

Delete the web site, then open the SMTP virtual server properties and open the “Access” tab.

Click the “Certificate” button and follow the wizard to import your PFX.

You can check that TLS has been enabled for receiving email by telnetting to your SMTP virtual server on port 25 and, after the SMTP banner has been displayed, enter “EHLO testserver”. In the list of data returned there should be two lines reading “TLS” and “STARTTLS” which mean your SMTP server is ready to use TLS security when receiving emails.

To send email to remote hosts with TLS enabled:
From the “Delivery” tab in the properties of your SMTP virtual server, select “Outbound Security” and tick “TLS Encryption” to enable TLS when sending email to remote servers.

NB: Enabling this option means the SMTP virtual server will require TLS support on ALL remote hosts it tries to send mail to. If TLS is not available, mail will sit in the outbound queue until it expires, an event log entry will be generated under the System event log and an NDR will be sent to the original sender of the email. You can work around this issue by using 2 SMTP virtual servers, one with TLS enabled, the other without, and setting up routing groups on your Exchange server to route outbound email via the TLS-enabled SMTP virtual server only if you are certain that the target domain supports TLS.

Want to change the default location Windows XP searches for its setup files if you’ve copied them from the CD to your hard drive?

Open Start -> Run -> regedit, browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and change the SourcePath value to the location of your setup files.