<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Geek &#187; Microsoft</title>
	<atom:link href="http://blog.wsiddique.com/category/networking/microsoft/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wsiddique.com</link>
	<description>who cares IT with thoughts</description>
	<lastBuildDate>Wed, 13 Jul 2011 06:44:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to dynamically create security-enhanced redirected folders by using folder redirection in Windows 2000 and in Windows Server 2003</title>
		<link>http://blog.wsiddique.com/networking/microsoft/active-directory/how-to-dynamically-create-security-enhanced-redirected-folders-by-using-folder-redirection-in-windows-2000-and-in-windows-server-2003/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/active-directory/how-to-dynamically-create-security-enhanced-redirected-folders-by-using-folder-redirection-in-windows-2000-and-in-windows-server-2003/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 02:23:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Recent]]></category>
		<category><![CDATA[2000]]></category>
		<category><![CDATA[2003]]></category>
		<category><![CDATA[Dynamic]]></category>
		<category><![CDATA[Folder]]></category>
		<category><![CDATA[Redirection]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=253</guid>
		<description><![CDATA[In Microsoft Windows 2000 and in Microsoft Windows Server 2003, as an administrator, you can customize desktops by using Folder Redirection. You can redirect the following folders by using Active...]]></description>
			<content:encoded><![CDATA[<p>In Microsoft Windows 2000 and in Microsoft Windows Server 2003, as an administrator, you can customize desktops by using Folder Redirection. You can redirect the following folders by using Active Directory and Group Policy:</p>
<ul>
<li>Application Data</li>
<li>Desktop</li>
<li>My Documents</li>
<li>My Documents/My Pictures</li>
<li>Start Menu</li>
</ul>
<p>You can find more information about Folder Redirection by searching Windows Help for <strong>Folder Redirection</strong>.</p>
<p>When you redirect folders to a shared location on a network, users need both read and write access to this location so that the users can read the contents these folders. However, in some scenarios, you may not want to grant read access.</p>
<div class="topOfPage"><strong><br />
Create security-enhanced redirected folders</strong></div>
<p>To make sure that only the user and the domain administrators have permissions to open a particular redirected folder, do the following:</p>
<ol>
<li>Select a central location in your environment where you would like to store Folder Redirection, and then share this folder. In this example, FLDREDIR is used.</li>
<li>Set <strong>Share Permissions</strong> for the Everyone group to <strong>Full Control</strong>.</li>
<li>Use the following settings for <strong>NTFS Permissions</strong>:
<ul>
<li><strong>CREATOR OWNER &#8211; Full Control </strong>(Apply onto: Subfolders and Files Only)</li>
<li><strong>System &#8211; Full Control</strong> (Apply onto: This Folder, Subfolders and Files)</li>
<li><strong>Domain Admins &#8211; Full Control </strong>(Apply onto: This Folder, Subfolders and Files)</li>
<li><strong>Everyone &#8211; Create Folder/Append Data</strong> (Apply onto: This Folder Only)</li>
<li><strong>Everyone &#8211; List Folder/Read Data</strong> (Apply onto: This Folder Only)</li>
<li><strong>Everyone &#8211; Read Attributes</strong> (Apply onto: This Folder Only)</li>
<li><strong>Everyone &#8211; Traverse Folder/Execute File </strong>(Apply onto: This Folder Only)</li>
</ul>
</li>
<li>Configure Folder Redirection Policy as outlined in Windows Help. Use a path similar to <strong>\\<em>server</em>\FLDREDIR\<em>username</em></strong> to create a folder under the shared folder, FLDREDIR.</li>
</ol>
<p>Because the Everyone group has the Create Folder/Append Data right, the group members have the proper permissions to create the folder; however, the members are not able to read the data afterwards. The Username group is the name of the user that was logged on when you created the folder. Because the folder is a child of the parent folder, it inherits the permissions that you assigned to FLDREDIR. Also, because the user is creating the folder, the user gains full control of the folder because of the Creator Owner Permission setting.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/active-directory/how-to-dynamically-create-security-enhanced-redirected-folders-by-using-folder-redirection-in-windows-2000-and-in-windows-server-2003/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tuning DNS Caching under Microsoft Windows</title>
		<link>http://blog.wsiddique.com/networking/microsoft/dns/tuning-dns-caching-under-microsoft-windows/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/dns/tuning-dns-caching-under-microsoft-windows/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 02:02:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Caching]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Tuning]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=241</guid>
		<description><![CDATA[You can modify the behavior of the Microsoft Windows DNS caching algorithm by setting two registry entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters registry key. The MaxCacheTtl represents the maximum time that the...]]></description>
			<content:encoded><![CDATA[<p>You can modify the behavior of the Microsoft Windows DNS caching algorithm by setting two registry entries in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters registry key.</p>
<p>The MaxCacheTtl represents the maximum time that the results of a DNS lookup will be cached. The default value is 86,400 seconds. If you set this value to 1, DNS entries will only be cashed for a single second.</p>
<p>MaxNegativeCacheTtl represents the maximim time that the results of a failed DNS lookup will be cached. The default value is 900 seconds. If you set this value to 0, failed DNS lookups will not be cached.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/dns/tuning-dns-caching-under-microsoft-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Turning off DNS Caching under Microsoft Windows</title>
		<link>http://blog.wsiddique.com/networking/microsoft/dns/turning-off-dns-caching-under-microsoft-windows/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/dns/turning-off-dns-caching-under-microsoft-windows/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 02:00:52 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Caching]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Turning off]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=239</guid>
		<description><![CDATA[If you experience frequent issues with DNS caching under Microsoft Windows , you can disable client-side DNS caching with either of these two commands: 1. net stop dnscache 2. sc...]]></description>
			<content:encoded><![CDATA[<p>If you experience frequent issues with DNS caching under Microsoft Windows , you can disable client-side DNS caching with either of these two commands:</p>
<p>1. net stop dnscache<br />
2. sc servername stop dnscache</p>
<p>This will disable DNS caching until the next reboot. To make the change permanent, use the Service Controller tool or the Services tool to set the DNS Client service startup type to Disabled.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/dns/turning-off-dns-caching-under-microsoft-windows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How do I Flush DNS?</title>
		<link>http://blog.wsiddique.com/networking/microsoft/dns/how-do-i-flush-dns/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/dns/how-do-i-flush-dns/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 01:59:17 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[DNS]]></category>
		<category><![CDATA[Flush]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=237</guid>
		<description><![CDATA[Most DNS clients cache the results of name resolution requests. This speeds up name resolution if multiple lookups are done to the same address, such as is common when browsing...]]></description>
			<content:encoded><![CDATA[<p>Most DNS clients cache the results of name resolution requests. This speeds up name resolution if multiple lookups are done to the same address, such as is common when browsing the web. Sometimes a bad DNS entry will be cached and you will need to either flush the DNS cache to get rid of it, or wait up to 24 hours for it to be dropped from the cache automatically.</p>
<p>In Microsoft Windows, you can use the command <strong>ipconfig /flushdns</strong> to flush the DNS resolver cache:<br />
<strong>C:\&gt;ipconfig /flushdns</strong><br />
Windows IP Configuration Successfully flushed the DNS Resolver Cache.</p>
<p>You can also use the command <strong>ipconfig /displaydns</strong> to view the DNS resolver cache.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/dns/how-do-i-flush-dns/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to use one Mailbox Manager recipient policy to move items to the Deleted Items folder and then to delete the items</title>
		<link>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-one-mailbox-manager-recipient-policy-to-move-items-to-the-deleted-items-folder-and-then-to-delete-the-items/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-one-mailbox-manager-recipient-policy-to-move-items-to-the-deleted-items-folder-and-then-to-delete-the-items/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 01:51:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Deleted]]></category>
		<category><![CDATA[Items]]></category>
		<category><![CDATA[Mailbox]]></category>
		<category><![CDATA[Manager]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=233</guid>
		<description><![CDATA[Problem description In Exchange 2000 and in Exchange 2003, a customer wanted to use one Mailbox Manager recipient policy to move items to the Deleted Items folder after 30 days....]]></description>
			<content:encoded><![CDATA[<h3 id="tocHeadRef"><strong>Problem description</strong></h3>
<p>In Exchange 2000 and in Exchange 2003, a customer wanted to use one Mailbox Manager recipient policy to move items to the Deleted Items folder after 30 days. Additionally, the customer wanted a second Mailbox Manager recipient policy to delete the items from the Deleted Items folder after five days. By design, only the highest priority recipient policy is applied. Therefore, if two recipient policies are created, only the first recipient policy is evaluated.</p>
<h4 id="tocHeadRef">Solution</h4>
<p>In Exchange System Manager, create one Mailbox Manager recipient policy to perform both actions. To do this, follow these steps:</p>
<ol>
<li>Specify the action to &#8220;move items to the Deleted Items folder&#8221; from any specified folders. This forces the items to be moved to the Deleted Items folder.</li>
<li>In the same policy, set the Age Limit for the Deleted Items folder. This forces Mailbox Manager to delete the items that have reached the age limit that is specified for the Deleted Items folder.</li>
</ol>
<p>This behavior occurs because the items that are moved to the Deleted Items folder cannot be moved to another folder. Instead, the items are deleted.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-one-mailbox-manager-recipient-policy-to-move-items-to-the-deleted-items-folder-and-then-to-delete-the-items/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to use recipient policies to control mailboxes in Exchange 2000 and Exchange 2003</title>
		<link>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-recipient-policies-to-control-mailboxes-in-exchange-2000-and-exchange-2003/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-recipient-policies-to-control-mailboxes-in-exchange-2000-and-exchange-2003/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 01:50:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[2000]]></category>
		<category><![CDATA[2003]]></category>
		<category><![CDATA[exchange]]></category>
		<category><![CDATA[Mailbox]]></category>
		<category><![CDATA[Policies]]></category>
		<category><![CDATA[Recipient]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=231</guid>
		<description><![CDATA[You can use recipient policies to control e-mail address settings and to manage mailboxes. This step-by-step article describes how to use the recipient policies feature of Mailbox Manager to automatically...]]></description>
			<content:encoded><![CDATA[<div>You can use recipient policies to control e-mail address settings and to manage mailboxes. This step-by-step article describes how to use the recipient policies feature of Mailbox Manager to automatically process the contents of users&#8217; mailboxes. Recipient policies come with preconfigurable options, including e-mail notification and automatic deletion of unwanted messages.</div>
<div><strong>Requirements</strong></div>
<div>
<p>The following list outlines the recommended hardware, software, network infrastructure, and service packs that you must have:</p>
<h4 id="tocHeadRef">Microsoft Exchange 2000 Server</h4>
<ul>
<li>Microsoft Windows 2000 Server with Service Pack 2 (SP2)</li>
<li>Active Directory</li>
<li>Exchange Server 2000 with Service Pack 1 (SP1)</li>
</ul>
<p><strong>Note</strong> The Mailbox Manager feature is available only after you apply Service Pack 1 (SP1) or later for Exchange 2000 Server.</p>
<h4 id="tocHeadRef">Microsoft Exchange Server 2003</h4>
<ul>
<li>Microsoft Windows 2000 Server with Service Pack 3 (SP3)</li>
<li>Active Directory</li>
<li>Exchange Server 2003</li>
<li>Exchange Server 2000 with Service Pack 1 (SP1)</li>
</ul>
<p>This article assumes that you are familiar with the following topics:</p>
<ul>
<li>Exchange System Manager</li>
<li>Recipient Update Service</li>
<li>The mailbox sizes that your users require to perform their jobs</li>
</ul>
<p><strong>Note</strong> For more information about how to use the Recipient Update Service in Exchange 2000, see the <a href="http://support.microsoft.com/kb/319188#10">REFERENCES</a> section.</p>
<div><strong><br />
A description of the Mailbox Manager recipient policy functionality</strong></div>
<p>Mailbox management recipient policies are a set of configurable rules that run on a schedule and that evaluate the mailboxes on the local server. The policy uses rules to filter all the recipient objects and to selectively apply mailbox management settings to messages in folders that go past the limit of the predefined rules.</p>
<p>The mailbox management process detects folders in a mailbox that contain messages larger than a certain size. If a message remains in a folder after a predefined time has passed (by default, 30 days), a number of predefined actions can be taken, including the following:</p>
<ul>
<li>Generate a report only and send the report to the mailbox owner.</li>
<li>Move the message to the Deleted Items folder.</li>
<li>Move the message to System Cleanup folders.</li>
<li>Delete the message immediately.</li>
</ul>
<p><strong>Note</strong> Use caution when you use the <strong>Delete the message immediately</strong> option, because users may have to recover their messages.</p>
<p>If you use recipient policies, it is easy to apply or revise the rules. You do not have to reconfigure settings individually on each object. You can also change recipient policy priority levels to change the way that multiple policies are adjusted.</p>
<p><strong>Note</strong> There is no default recipient policy for mailbox management (unlike the e-mail recipient policies). However, you can add the required property page to the default recipient policy if you want to create a mailbox management policy that applies to all recipients.</p>
<p>Policies are applied according to the schedule that you set up on each server. This prevents mailbox management from running on all servers in the organization at the same time. However, you can force a manual update if you want a recipient policy to apply immediately.</p>
<p><strong>Note</strong> Like e-mail recipient policies, the highest priority recipient policy that applies to an Exchange Server object is the effective policy. Lower priority policies are no longer evaluated after a match has been made.</p>
<div><strong>Use recipient policies for mailbox management</strong></div>
<p>When you use mailbox management recipient policies, you can configure a filter rule that specifies the subset of messaging-enabled objects that the recipient policy applies to. The recipient policy is then applied to objects that match the filter conditions. This is useful when you have a subset of users who have different storage requirements. For example, there may be a technical author in your organization who regularly sends out very large attachments that must be stored. You can use a less restrictive mailbox management policy for this user. <strong>Note</strong> You can configure mailbox storage limits to obtain a similar result. However, make sure that you note the following differences between mailbox storage limits and mailbox management recipient policies:</p>
<ul>
<li>Mailbox storage limits limit the total size of the mailbox.</li>
<li>Mailbox management recipient policies limit messages over a certain size.</li>
</ul>
<p>For more information about how to configure storage limits, click the following article number to view the article in the Microsoft Knowledge Base:</p>
<div><a href="http://support.microsoft.com/kb/319583/">319583</a> (http://support.microsoft.com/kb/319583/ ) How to configure storage limits on mailboxes in Exchange 2000</div>
<div><strong>Create a mailbox management recipient policy</strong></div>
<p><strong><br />
Note</strong> Before you create a new recipient mailbox management policy, you must determine the following:</p>
<ul>
<li>What limits you want the policy to enforce.</li>
<li>What group you want the policy to control.</li>
<li>How you want the policy to handle messages that go past policy limits.</li>
</ul>
<p>The following procedure configures a mailbox limit for users in the accounts department of a test environment.</p>
<p>To create a mailbox management recipient policy, follow these steps:</p>
<ol>
<li>Click <strong>Start</strong>, point to <strong>Programs</strong>, point to <strong>Microsoft Exchange</strong>, and then click <strong>System Manager</strong>.</li>
<li>In the left pane of Exchange System Manager, expand the <strong>Recipients</strong> object, right-click <strong>Recipient Policies</strong>, point to <strong>New</strong>, and then click <strong>Recipient Policy</strong>.The <strong>New Policy</strong> dialog box appears.</li>
<li>Click to select the <strong>Mailbox Manager Settings</strong> check box, and then click <strong>OK</strong>.<strong>Note</strong> If you do not see the option for Mailbox Manager Settings, reapply the Exchange service pack. It may not have been correctly applied.</li>
<li>The <strong>Properties</strong> dialog box appears. Type a name for the recipient policy in the <strong>Name</strong> box.<strong>Note</strong> We recommend that you use a descriptive name, such as &#8220;Accounts Department Mailbox Settings.&#8221;</li>
<li>Click <strong>Modify</strong>.The <strong>Find Exchange Recipients</strong> dialog box appears.</li>
<li>Click the <strong>General</strong> tab. In this example, mailbox management settings apply only to accounts that have an Exchange mailbox. Therefore, click to clear the <strong>Users with external e-mail addresses</strong> check box, the <strong>Groups</strong> check box, the <strong>Contacts</strong> check box, and the <strong>Public Folders</strong> check box to exclude these groups from the recipient policy.</li>
<li>Click the <strong>Storage</strong> tab to configure mailbox management recipient policies that are specific to a particular Exchange 2000 computer. Then, do one of the following:
<ul>
<li>Click <strong>Mailboxes on this server</strong>, and then click <strong>Browse</strong>. The <strong>Select Exchange Server</strong> list box appears. Select the server that you want to use, and then click <strong>OK</strong>.</li>
<li>Click <strong>Mailboxes in this mailbox store</strong>, click <strong>Browse</strong> to search for a store, and then click <strong>OK</strong>.</li>
</ul>
</li>
<li>Click the <strong>Advanced</strong> tab, and then click <strong>Field</strong>. You can now select any of the following options:
<ul>
<li><strong>User</strong></li>
<li><strong>Contact</strong></li>
<li><strong>Group</strong></li>
<li><strong>Public Folder</strong></li>
</ul>
</li>
<li>For this example, click <strong>User</strong>, and then click <strong>Department</strong> to select <strong>Department</strong> in the field value.</li>
<li>Under <strong>Condition</strong>, click any of the following:
<ul>
<li><strong>Starts with</strong></li>
<li><strong>Ends with</strong></li>
<li><strong>Is (exactly)</strong></li>
<li><strong>Is not</strong></li>
<li><strong>Present</strong></li>
<li><strong>Not present</strong></li>
</ul>
</li>
<li>If you click <strong>Starts with</strong>, <strong>Ends with</strong>, <strong>Is (exactly)</strong>, or <strong>Is not</strong> as your condition, type a value in the <strong>Value</strong> field. For example, click <strong>Is (exactly)</strong>, and then type <var>Accounts</var> to find all employees who work for the accounts department.</li>
<li>Click <strong>Add</strong> to add the condition to the list.<strong>Note</strong> You can add additional conditions, but remember that all conditions must be true for a match to be displayed.</li>
<li>After you have finished adding conditions, click <strong>Find Now</strong>.Any matches to the conditions are displayed in the new list that appears in the <strong>Find Exchange Recipients</strong> dialog box.</li>
<li>If the list displays the correct users for this recipient policy, click <strong>OK</strong>. If not, revise the search conditions until your search displays the correct users for this recipient policy.</li>
<li>Click <strong>OK</strong>. You receive the following message:
<div>When a recipient policy filter changes it does not mean that proxy addresses for recipients who may no longer be under the control of the policy will be automatically re-evaluated. For these recipients to receive proxies from the new policies that they belong to, use &#8216;Apply this policy now&#8217; on the policies that now affect these recipients.</div>
<p>This message does not affect mailbox management recipient policies. Click <strong>OK</strong>.</li>
<li>Under <strong>Filter rules</strong>, the LDAP filter statement shows the current filter rule. Click the <strong>Mailbox Manager Settings (Policy)</strong> tab.<strong>Note</strong> If the <strong>Mailbox Manager Settings (Policy)</strong> tab is not available after you apply Exchange 2000 Server SP1, right-click the recipient policy, click <strong>Change Property Pages</strong>, and then click to select the <strong>Mailbox Manager Settings</strong> check box.</li>
<li>Under <strong>When processing a mailbox</strong>, click one of the following options for handling messages that go past the policy limits:
<ul>
<li><strong>Generate report only</strong></li>
<li><strong>Move items to Deleted Items folder</strong></li>
<li><strong>Move to System Cleanup folder</strong></li>
<li><strong>Delete immediately</strong><strong>Note</strong> Use caution when you use the <strong>Delete the message immediately</strong> option on folders, because users may have to recover their messages.</li>
</ul>
</li>
<li>In the list of folders, select the folder that you want to configure, and then click <strong>Edit</strong>.</li>
<li>In the <strong>Folder Retention Settings</strong> dialog box, type an age limit when you want the selected processing action to occur, specify a size limit for the messages that you want the action to apply to, and then click <strong>OK</strong>.For example, if you type 90 and 2048, all messages that are older than 90 days and over 2 megabytes (MB) are processed.</li>
<li>Repeat steps 18 and 19 for each folder in the list that you want to configure.</li>
<li>Click <strong>Send notification mail to users after processing</strong> if you want to send users an e-mail message notifying them when their mailboxes have been processed. Click <strong>Message</strong> to edit the notification message.</li>
<li>Click the <strong>Insert the number of messages processed</strong> check box if you want a summary of the number of oversize messages processed. Click <strong>OK</strong> to return to the <strong>Properties</strong> dialog box.</li>
<li>If you want to exclude certain message classes (for example, to prevent the processing task reports), click the <strong>Exclude specific message classes</strong> box, and then click <strong>Customize</strong>. The <strong>Message Classes</strong> dialog box appears. Type a message class in the <strong>Exclude Message Classes</strong> field. For example, type <var>IPM.Task</var>, and then click <strong>Add</strong>. Add all the classes you want to exclude.Message class types include:
<ul>
<li>Calendar IPM.Appointment</li>
<li>Contacts IPM.Contact</li>
<li>Inbox IPM.Note</li>
<li>Journal IPM.Activity</li>
<li>Notes IPM.StickyNote</li>
<li>Tasks IPM.Task</li>
<li>Meeting Requests IPM.Schedule.Meeting.Request</li>
</ul>
<p>For a full list of message classes, visit the following Microsoft Web site:<br />
<a href="http://msdn2.microsoft.com/en-us/library/aa262246(office.10).aspx">http://msdn2.microsoft.com/en-us/library/aa262246(office.10).aspx</a> (http://msdn2.microsoft.com/en-us/library/aa262246(office.10).aspx)</li>
<li>After you have finished adding message classes, click <strong>OK</strong> to return to the <strong>Properties</strong> dialog box.</li>
<li>Click <strong>OK</strong> to close the <strong>Properties</strong> dialog box.The new mailbox management recipient policy is displayed in the right pane in Exchange System Manager.</li>
</ol>
<div><strong>Configure mailbox management at the server level</strong></div>
<p>To schedule the day and time when a policy will run, change the settings at a server level. To do this, follow these steps:</p>
<ol>
<li>Click <strong>Start</strong>, point to <strong>Programs</strong>, point to <strong>Microsoft Exchange</strong>, and then click <strong>System Manager</strong>.</li>
<li>In the left pane of <strong>Exchange System Manager</strong>, expand the <strong>Servers</strong> object.</li>
<li>Right-click the computer that you want to configure, and then click <strong>Properties</strong>. The <strong><var>Servername</var></strong> Properties dialog box appears.</li>
<li>Click the <strong>Mailbox Management</strong> tab to display the current settings.</li>
<li>Under <strong>Start mailbox management process</strong>, do one of the following:
<ul>
<li>Click the drop-down list to select a time for the mailbox management to run.</li>
<li>Click <strong>Customize</strong>, click a day in the left column, and then click a time on the top row. After you select the times that you want, click <strong>OK</strong>.</li>
</ul>
</li>
<li>Click <strong>Reporting</strong> to select the type of report (either a detailed report or a summary) to create when mailboxes are processed. You must also select a recipient to receive the reports. Click <strong>Browse</strong>, select a recipient, and then click <strong>OK</strong>. <strong>Note</strong> You cannot send reports to distribution lists.</li>
<li>Click <strong>OK</strong> to accept the mailbox management settings.</li>
</ol>
<div><strong>Manually run mailbox management</strong></div>
<p>To run mailbox management immediately, follow these steps:</p>
<ol>
<li>Click <strong>Start</strong>, point to <strong>Programs</strong>, point to <strong>Microsoft Exchange</strong>, and then click <strong>System Manager</strong>.</li>
<li>In the left pane of Exchange System Manager, expand the <strong>Servers</strong> object.</li>
<li>Right-click the computer that you want to process, and then click <strong>Start Mailbox Management Process</strong>.Mailbox management starts after a short delay, depending on the current resource utilization on that computer.</li>
</ol>
<p><strong>Note</strong> Avoid using the mailbox management process when the system is busy, because this may affect server performance.</p>
<div><strong>Confirm that your new mailbox management policy works correctly</strong></div>
<p>To confirm that your new mailbox management policy works, follow these steps:</p>
<ol>
<li>Create a test Exchange user account.</li>
<li>Configure the filter rule so that the recipient policy applies only to the test account.</li>
<li>Import old and large messages to the test account.</li>
<li>Run the mailbox management process manually from the server.</li>
</ol>
<p>If your new mailbox management policy works, messages are moved according to the policy settings, and you receive the notification message as configured in the policy. <strong>Note</strong> Mailbox Manager does not process mailboxes in the priority order that the mailbox management recipient policies are applied. When Mailbox Manager runs, it iterates through all the private stores on the server, and then iterates through all the mailboxes in each store. Each mailbox is cleaned based on the recipient policy that is applied to the user object for that mailbox in the Active Directory directory service by the Recipient Update Service. The order or priority of the recipient policies does not affect the order that the mailboxes are processed</p>
<div><strong>Troubleshooting</strong></div>
<p>The most common errors that occur when you use recipient policies to control mailboxes occur because of incorrectly configured filters. For example, if you configure Mailbox Manager to send detailed reports or summary reports to the administrator&#8217;s mailbox after mailbox management is complete, when you start the mailbox cleanup process manually or the mailbox cleanup process starts according to its schedule, an administrative report may not be generated. Confirm that the filters are configured correctly by following the steps in the <a href="http://support.microsoft.com/kb/319188#5">Create a mailbox management recipient policy</a> section. Make sure that the filter produces the expected results when you click <strong>Find Now</strong> in the <strong>Find Exchange Recipients</strong> dialog box.</p>
<p>Another common issue occurs when policies do not apply as you expect. This can be caused by overlapping policies. Only one mailbox recipient policy can be applied to each user. If you have more than one recipient policy applied to a user, make sure that the recipient policy membership does not overlap. If two mailbox recipient policies are applied to the same user, the priority of the recipient policies determines which recipient policy is used.</p>
</div>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-use-recipient-policies-to-control-mailboxes-in-exchange-2000-and-exchange-2003/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to change Mailbox store path at existing user profile in AD?</title>
		<link>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-change-mailbox-store-path-at-existing-user-profile-in-ad/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-change-mailbox-store-path-at-existing-user-profile-in-ad/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 01:45:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Change]]></category>
		<category><![CDATA[Mailbox]]></category>
		<category><![CDATA[profile]]></category>
		<category><![CDATA[Store]]></category>
		<category><![CDATA[user]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=228</guid>
		<description><![CDATA[Solution: Make sure the user is not connected with the Mailbox that you want to move Now follow the steps below: 1)Right Click the AD user and select Exchange Tasks...]]></description>
			<content:encoded><![CDATA[<p><strong>Solution:</strong> Make sure the user is not connected with the Mailbox that you want to move<br />
Now follow the steps below:</p>
<p>1)Right Click the AD user and select Exchange Tasks<br />
2)Click Next on the Welcome screen<br />
3)Highlight &#8220;Move Mailbox&#8221; and click next<br />
4)Select the correct Server and Mailbox Store and click next<br />
5)Wait for the move and follow the on screen instructions</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-change-mailbox-store-path-at-existing-user-profile-in-ad/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Save queries in Windows Server 2003’s Active Directory Users and Computers tool</title>
		<link>http://blog.wsiddique.com/networking/microsoft/active-directory/save-queries-in-windows-server-2003%e2%80%99s-active-directory-users-and-computers-tool/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/active-directory/save-queries-in-windows-server-2003%e2%80%99s-active-directory-users-and-computers-tool/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 04:40:27 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Active Directory]]></category>
		<category><![CDATA[Queries Active Directory Computer Tool]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=214</guid>
		<description><![CDATA[Windows Server 2003 administrators can’t live without the Active Directory Users and Computers tool. Here’s a quick look at the saved queries portion of the tool, which allows you to...]]></description>
			<content:encoded><![CDATA[<p>Windows Server 2003 administrators can’t live without the Active Directory Users and Computers tool. Here’s a quick look at the saved queries portion of the tool, which allows you to save and reuse lookups for different Active Directory (AD) objects. The ability to reuse queries can save time and speed up the process of locating objects within your AD environment.</p>
<p>The Active Directory Users and Computers tool is included in the AD implementation used by Windows Server 2003. The following steps will help in saving AD queries:</p>
<ol>
<li>Open Active Directory Users And Computers.</li>
<li>Right-click the Saved Queries folder in the left pane of the window.</li>
<li>Select New and choose Query.</li>
<li>Enter a name and description for your saved query. (The description is optional, but it can help you remember what the query is looking for if you ever need to revisit the query definition.)</li>
<li>Click the Define Query button, which will open the Common Queries window. (You’ll find that Microsoft has created a few predefined queries to assist you in finding certain objects. For this example, we will create our own query to find any users whose last names are similar to Miller.)</li>
<li>In the Find box, select Users, Contacts, And Groups.</li>
<li>Select the Advanced tab.</li>
<li>Click the Field button, select User, and then select Last Name.</li>
<li>For an operator in the center list box, select Is Like.</li>
<li>Enter <em>Miller or Mille*</em> in the final text box on the row and click Add.</li>
<li>Click OK in the Define Query window to return to the New Query window. (In the New Query window, you can also choose to include sub containers. Selecting this will search in any child organizational units or container objects for things that meet the conditions of the query you created.)</li>
<li>Click OK to close the New Query window and return to Active Directory Users And Computers.</li>
</ol>
<p>Your query will appear saved beneath Saved Queries in the left pane of the console. To execute the query, right-click it and choose Refresh. If you select the query without refreshing, the results from the last time you ran the query will appear.</p>
<p>This method does not circumvent or remove the need for Active Directory Users and Computers, but it may make it a little more useful. Remember that you can create truly custom queries for all of the AD object properties in your environment.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/active-directory/save-queries-in-windows-server-2003%e2%80%99s-active-directory-users-and-computers-tool/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to configure a mailbox to forward mail to a mail-enabled contact</title>
		<link>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-configure-a-mailbox-to-forward-mail-to-a-mail-enabled-contact/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-configure-a-mailbox-to-forward-mail-to-a-mail-enabled-contact/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 04:22:05 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Exchange]]></category>
		<category><![CDATA[Configure Mailbox Forward Mail Enabled Contact]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=202</guid>
		<description><![CDATA[This article describes how to configure a mailbox to forward mail to either a mail-enabled contact (a custom recipient in Exchange Server 5.5) or another mailbox on an Exchange 2000...]]></description>
			<content:encoded><![CDATA[<p>This article describes how to configure a mailbox to forward mail to either a mail-enabled contact (a custom recipient in Exchange Server 5.5) or another mailbox on an Exchange 2000 computer or on an Exchange Server 2003 computer.</p>
<p><strong>Note</strong> This procedure must be performed on a computer that is running both Exchange System Manager and the Active Directory Users and Computers snap-in. The Exchange Server-specific options are not available if the computer is not running the DLL files that are installed with Exchange System Manager.</p>
<p>The procedure is divided into two separate sections. If you are only going to be forwarding mail from one Exchange 2000 or Exchange 2003 mailbox or user to another Exchange 2000 or Exchange 2003 mailbox user, you do not have to complete the following first or second sections.</p>
<p><strong>How to create a contact</strong></p>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td>1.</td>
<td>Start the Active Directory Users and Computers snap-in.</td>
</tr>
<tr>
<td>2.</td>
<td>Expand the server, and then right-click <strong>Users</strong>.</td>
</tr>
<tr>
<td>3.</td>
<td>Click <strong>New</strong>, and then click <strong>Contact</strong>.</td>
</tr>
<tr>
<td>4.</td>
<td>Type a name.</td>
</tr>
<tr>
<td>5.</td>
<td>Click <strong>Modify</strong>, click <strong>SMTP</strong>, and then click <strong>OK</strong> to create the custom SMTP mail address.</td>
</tr>
<tr>
<td>6.</td>
<td>Type the SMTP e-mail address, click <strong>OK</strong>, click <strong>Next</strong>, and then click <strong>Finish</strong>.</td>
</tr>
</tbody>
</table>
<p><strong>How to mail-enable a contact</strong></p>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td>1.</td>
<td>Start the Active Directory Users and Computers snap-in.</td>
</tr>
<tr>
<td>2.</td>
<td>Right-click the contact, and then click <strong>Exchange Tasks</strong>.</td>
</tr>
<tr>
<td>3.</td>
<td>Click <strong>Next</strong>, click to select <strong>Establish e-mail addresses</strong>, and then click <strong>Next</strong>.</td>
</tr>
<tr>
<td>4.</td>
<td>If the contact does not have an alias, enter an alias for the contact.</td>
</tr>
<tr>
<td>5.</td>
<td>Click the appropriate e-mail address type, and then type the e-mail address.<strong>Note</strong> Click the <strong>Advanced</strong> tab to configure the <strong>Message Format</strong> setting.</td>
</tr>
<tr>
<td>6.</td>
<td>Click <strong>OK</strong>, click <strong>Next</strong>, and then click <strong>Finish</strong>.</td>
</tr>
</tbody>
</table>
<p><strong>How to configure mail forwarding</strong></p>
<p><strong>Note</strong> The forwarding address can be any mail-enabled object. Examples of mail-enabled objects include distribution groups, security groups, public folders, and other related items.</p>
<table border="0" cellpadding="0">
<tbody>
<tr>
<td>1.</td>
<td>Start the Active Directory Users and Computers snap-in.</td>
</tr>
<tr>
<td>2.</td>
<td>Right-click the mail-enabled user, and then click <strong>Properties</strong>.</td>
</tr>
<tr>
<td>3.</td>
<td>Click the <strong>Exchange General</strong> tab.</td>
</tr>
<tr>
<td>4.</td>
<td>Click <strong>Delivery Options</strong>.</td>
</tr>
<tr>
<td>5.</td>
<td>In the <strong>Forwarding Address</strong> section, click <strong>Forward to</strong>, and then click <strong>Modify</strong>.</td>
</tr>
<tr>
<td>6.</td>
<td>Click the mail-enabled user or the mail-enabled contact. Then, click <strong>OK</strong>.<strong>Note</strong> If you want e-mail to be delivered to the original mailbox as well as the forwarding address, select the <strong>Deliver messages to both forwarding address and mailbox</strong> check box.</td>
</tr>
<tr>
<td>7.</td>
<td>To close <strong>Delivery Options</strong> and to close <strong>Properties</strong>, click <strong>OK</strong> two times.</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/exchange-microsoft-networking/how-to-configure-a-mailbox-to-forward-mail-to-a-mail-enabled-contact/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Schedule Windows server to reboot or shutdown automatically</title>
		<link>http://blog.wsiddique.com/networking/microsoft/servers/schedule-windows-server-to-reboot-or-shutdown-automatically/</link>
		<comments>http://blog.wsiddique.com/networking/microsoft/servers/schedule-windows-server-to-reboot-or-shutdown-automatically/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 04:14:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Servers]]></category>
		<category><![CDATA[Shutdown Windows Server Schedule]]></category>

		<guid isPermaLink="false">http://blog.wsiddique.com/?p=197</guid>
		<description><![CDATA[Sometime it is necessary to reboot (or shutdown) windows server. Under UNIX or Linux you can use reboot / hal t/shutdown command via cron jobs or at command. But, when...]]></description>
			<content:encoded><![CDATA[<p>Sometime it is necessary to reboot (or shutdown) windows server. Under UNIX or Linux you can use <a href="http://www.cyberciti.biz/tips/howto-shutdown-linux-box-automatically.html">reboot / hal t/shutdown command via cron jobs</a> or at command. But, when it comes to Windows server there is no built in command exist. Only Windows 2000 Resource Kit offers shutdown command line utility.</p>
<p>However, sysinternals has nifty utility called PsShutdown. It is a command-line utility similar to the shutdown utility from the Windows 2000 Resource Kit, but with the ability to do much more. In addition to supporting the same options for shutting down or rebooting the local or a remote computer, PsShutdown can logoff the console user or lock the console (locking requires Windows 2000 or higher). PsShutdown requires no manual installation of client software.</p>
<h2>How do I schedule Windows Server Reboot / Shutdown?</h2>
<p>You can download <a href="http://www.sysinternals.com/utilities/psshutdown.html">PsShutdown</a> from <a href="http://www.sysinternals.com/">sysinternals</a> web site.</p>
<p>Store file on Windows server in folder. I use folder called C:\admutils. Next open windows command prompt (Start &gt; Run &gt; cmd) and use windows at command to schedule reboot:<br />
<code>c:&gt; at 2:00am c:\admutils\psshutdown.exe -r -f -c -t 10</code><br />
Above command will reboot system at 2am. If you want to shutdown system:<br />
<code>c:&gt; at 1:00am c:\admutils\psshutdown.exe -s -f -c -t 10</code><br />
Where,</p>
<ul>
<li>-s: Shutdown windows server</li>
<li>-r: Reboot windows server</li>
<li>-f: Forces all running application to exit</li>
<li>-c: Allow the shutdown to by cancel by user</li>
<li>-t: Specifies the countdown in seconds until the shutdown</li>
</ul>
<p>I dont think there is a solution to reboot through AD&#8230;but here is a good way to do it&#8230;.</p>
<p>If you are doing it during work hours use the shutdown.exe command that is free from Microsoft&#8230;simply enter&#8230;</p>
<p>shutdown.exe \\PCNAME /R /T:10 &#8220;Message&#8221; /C</p>
<p>/R &#8211; Reboots the machine<br />
/T:10 &#8211; give it 10 seconds for anyone to save work if they need to (Can be whatever time)<br />
&#8220;Message&#8221; &#8211; a message to any users on the PC at the time. (Eg you have 30 seconds)<br />
/C &#8211; Causes all porgrams open to close down</p>
<p>You can create a scheduled task to do this out of hours by putting this (shutdown.exe \\PCNAME /R /T:10 &#8220;Message&#8221; /C) in the Run part of the scheduled task</p>
<p>To do this to lots of PC&#8217;s at the same time do a simple command script&#8230;.</p>
<p>Put the shutdown.exe file on the c: drive<br />
Create PClist.txt file on the C: Drive</p>
<p>Create a txt file and rename the .txt part at the end of the file .cmd</p>
<p>right click and select edit and type in there&#8230;.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;-</p>
<p>@Echo Off</p>
<p>SET PCNAMES=&#8221;C:PCList.txt&#8221;</p>
<p>FOR /F %%a IN (%PCNAMES%) DO CaLL :DODEL %%a</p>
<p>GOTO :EOF</p>
<p>:DODEL<br />
SET BRSVR=%1<br />
ECHO %BRSVR%</p>
<p>C:\shutdown.exe  \\%PCNAMES% /R /T:10 &#8220;Message&#8221; /C</p>
<p>&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>In the PCList put in the names of the PC&#8217;s for example&#8230;.</p>
<p>Server01<br />
PC01<br />
Laptop01</p>
<p>Then click the cmd script and this will apply this to all the pc&#8217;s and restart each of them</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wsiddique.com/networking/microsoft/servers/schedule-windows-server-to-reboot-or-shutdown-automatically/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

