# Sunday, February 12, 2006

To remotely enable RDP connections open network registry in Regedit and ensure that
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnection is set to 0.

To speed up the logon process over slow links delete any value in
HKEY_USERS\.DEFAULT\Control Panel\Desktop\Wallpaper.

connect to console:i:1
server port:i:3389 (or in full address)
full address:s:[IP address|host:(port)]

(see: http://support.microsoft.com/default.aspx?scid=kb;en-us;885187)

win
Sunday, February 12, 2006 12:06:35 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Saturday, February 11, 2006

RFC 2068 stipulates two concurrent download sessions.  IE allows two such sessions (plus one queued).  To increase this to 10, in:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings

add the following DWORD values:

Value name: MaxConnectionsPer1_0Server
Value data: 10
Base: Decimal

Value Name: MaxConnectionsPerServer
Value data: 10
Base: Decimal


Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"MaxConnectionsPer1_0Server"=dword:00000010
"MaxConnectionsPerServer"=dword:00000010
 

ie
Saturday, February 11, 2006 1:45:43 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback

This refers to OWA 2003 access to freedocs, documents that are shared as standalone items in a folder.

The shared item is not an attachment to a post; rather, it is considered a "free document" or freedoc for short.Freedocs are not new to Exchange 2003; they are present in all prior versions of Exchange. However, Exchange 2000 made them more useful by making them accessible via OWA URLs (e.g., http://server/public/exchange2003/intro_e2k3.doc). Microsoft made a security-related change to Exchange 2003 that is blocking OWA access to freedocs.

There is a registry entry you can add to your OWA servers that re-enables OWA access to freedocs:

Location: HKLM\System\CurrentControlSet\Services\MSExchangeWeb\OWA
Value: EnableFreedocs
Type: REG_DWORD
Value: 0, 1, 2 or 3 (dec)

If this value is not present or set to 0, freedocs are completely blocked in OWA. This entry is not present by default, so freedocs are blocked out-of-the-box in OWA 2003. When set to 1, freedocs are only accessible when accessed directly via a back-end server; freedocs will not accessible to OWA users connecting through a front-end server. If you set the value to 2, freedocs are accessible from back-end servers, and from any front-end server configured with a Host Header entry that matches the following registry on the back-end server:

Location: HKLM\System\CurrentControlSet\Services\MSExchangeWeb\OWA
Value: AcceptedAttachmentFrontEnds
Type: REG_SZ
Value: comma-delimited list of FE servers
(e.g., fesvr1.domain.com, fesvr2.domain.com, etc)

Finally, when EnableFreedocs is set to 3, they are accessible to all OWA users.

owa
Saturday, February 11, 2006 12:55:33 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Sunday, February 05, 2006

Download this zip and extract into dasBlog root directory.  Remember to give NETWORK SERVICE (2003) read access to these files and the \code directory.

Then add http://.../PublicReferrers.aspx link to a sidebar in homeTemplate.blogtemplate.

Courtesy of jelle druyts

Sunday, February 05, 2006 2:52:21 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback

To have certain links opening in a new window (and to be HTML 4.0 & XHTML 1.0 Strict compliant) use the following procedure:

1.   Create text file "external.js" containing:

function externalLinks() { 
 if (!document.getElementsByTagName) return;
 var anchors = document.getElementsByTagName("a");
 for (var i=0; i<anchors.length; i++) {
   var anchor = anchors[i];
   if (anchor.getAttribute("href") &&
       anchor.getAttribute("rel") == "external")
     anchor.target = "_blank";
 }
}
window.onload = externalLinks;

and save this in a new directory "\scripts"

2.   Edit header secion of "homeTemplate.blogtemplate" to contain:

<script type="text/javascript" src="scripts/external.js"></script>

3.    Using dasBlog's native editor (in HTML section) edit links to be in the following format:

<a href="document.html" rel="external">external link text</a>

For example:

BBC News site in new window

 

Update Regardless of tab settings, in Firefox links always seem to want to open in the same tab. The only way to force them to open in a new tab is to include the javascript in the document rather than a link to an external .js file.
Sunday, February 05, 2006 1:45:18 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, February 03, 2006

First create, mail-enable and grant appropriate permissions to the public folder.

To grant a user the Send As permissions for a public folder, follow these steps:

1.

Start Exchange System Manager, and then locate the public folder.

2.

Right-click the public folder, and then click Properties.

3.

Click the Permissions tab, and then click Directory rights.

4.

Add the user who you want to grant Send As permissions to, and then click the user in the Name list.

5.

In the Allow column of the Permissions list, click to select the Send As check box.

6.

Click Apply, and then click OK.

7.

Right-click the public folder that you created, and then click Properties.

8.

Under Exchange Advanced, click to clear the hide from Exchange address lists check box.

9.

Type a name for the alias in the simple display name box.

10.

Click OK.

Then rebuild the OAB and download to clients.

Friday, February 03, 2006 3:09:02 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback