<?xml version='1.0' encoding='UTF-8'?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-5167218407419816194</id><updated>2008-02-08T11:10:19.579-06:00</updated><title type='text'>Nerd | Notes</title><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default'/><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml'/><author><name>J</name></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>9</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-9129928374486971525</id><published>2008-02-08T11:05:00.000-06:00</published><updated>2008-02-08T11:08:48.368-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Exchange'/><category scheme='http://www.blogger.com/atom/ns#' term='Active Directory'/><title type='text'>Associate an Exchange Mailbox with a new User</title><summary type='text'>Occasionally you will need to move an existing Exchange 2003 mailbox from one user to another.  This may be the result of employee turn over or change of responsibilities.  To move the mailbox, you must first detach it from the current user account.  To detach a mailbox you will use the Exchange Tasks wizard in Active Directory to delete the mailbox.  In Exchange 2003, deleted mailboxes are not </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2008/02/associate-exchange-mailbox-with-new.html' title='Associate an Exchange Mailbox with a new User'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/9129928374486971525'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/9129928374486971525'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-5656979116955585889</id><published>2008-01-21T12:13:00.000-06:00</published><updated>2008-01-21T12:35:46.871-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Cisco'/><title type='text'>Removing a Provisioned Switch from a Switch Stack</title><summary type='text'>  &lt;!--   @page { size: 8.5in 11in; margin: 0.79in }   P { margin-bottom: 0.08in }  --&gt;     When a provisioned switch is removed from a switch stack, the member number must be manually changed back to 1 and the provision information must be removed from the switch.  If you try to remove the provision information from the switch before the member number has been reset to 1, you may receive the </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2008/01/removing-provisioned-switch-from-switch.html' title='Removing a Provisioned Switch from a Switch Stack'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/5656979116955585889'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/5656979116955585889'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-4154043564313617158</id><published>2008-01-16T21:05:00.000-06:00</published><updated>2008-01-21T12:36:44.032-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Cisco'/><title type='text'>MAC Access Lists</title><summary type='text'>Just as we can create access lists based on IP addresses, we can also create access lists based on MAC addresses.  The first section sets up an extended access list based on MAC address named mac_filter.  It then adds an allow statement for a single host with the MAC address 00 00 00 00 00 00, and allows it access to any other host.  This is followed by a deny any any, which will deny any other </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2008/01/mac-address-based-access-lists.html' title='MAC Access Lists'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/4154043564313617158'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/4154043564313617158'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-34147146507673971</id><published>2008-01-10T18:35:00.000-06:00</published><updated>2008-01-21T12:38:19.469-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Cisco'/><title type='text'>Auto-Negotiation Required for Auto-MDIX</title><summary type='text'>Auto-MDIX allows connectivity between Cisco devices (and other vendors that support the HP Auto-MDIX standard) with a straight-through cable. In IOS version 12.2.18 and higher, Auto-MDIX is enabled by default on all interfaces. It is however, a requirement of Auto-MDIX, that auto-negotiation be enabled. This means that Auto-MDIX will be disabled on any interface were the duplex mode or line speed</summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2008/01/auto-negotiation-required-for-auto-mdix.html' title='Auto-Negotiation Required for Auto-MDIX'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/34147146507673971'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/34147146507673971'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-5765359413981261628</id><published>2007-12-31T11:34:00.000-06:00</published><updated>2007-12-31T12:09:39.428-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Outlook'/><title type='text'>Creating an Empty Copy of an Outlook Personal Folder Hierarchy</title><summary type='text'>Have you ever needed to duplicate a personal folder hierarchy in Outlook without duplicating the messages contained in the original folder hierarchy?  For example, you may want to create a 2008 folder and copy all of the subfolders from your 2007 folder into the 2008 folder.  This is very straightforward and can be done by right clicking on the folder, selecting copy �??folder_name�??, and following </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2007/12/creating-empty-copy-of-outlook-personal.html' title='Creating an Empty Copy of an Outlook Personal Folder Hierarchy'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/5765359413981261628'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/5765359413981261628'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-4151021339404070797</id><published>2007-12-29T22:46:00.000-06:00</published><updated>2007-12-29T22:52:45.001-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Group Policy'/><category scheme='http://www.blogger.com/atom/ns#' term='Internet Explorer'/><title type='text'>IE Security Zones, A Registry Roadmap</title><summary type='text'>Here is a very useful collection of registry keys and values that you can leverage to configure Internet Explorer.  In my environment, we use Desktop Standard's Policy Maker to push registry changes with Group Policy.
  For those of you not familiar with Policy Maker, it is an application that snaps into the GPMC (Group Policy Management Console) and allows you to push individual registry changes</summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2007/12/ie-security-zones-registry-roadmap.html' title='IE Security Zones, A Registry Roadmap'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/4151021339404070797'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/4151021339404070797'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-6092900950976313143</id><published>2007-12-29T16:43:00.000-06:00</published><updated>2007-12-30T18:41:09.449-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Exchange'/><title type='text'>Delivering Email to Disabled Accounts</title><summary type='text'>When using MS Exchange, mail sent to a disabled account bounces.  If you need to allow mail to be delivered to the inactive user's mailbox, you will need to grant SELF the Associated External Account permission.  This is probably the best solution, if you only have to manage a small number of mailboxes or if you sometimes choose to bounce the mail.  If your policy is to always accept the mail, </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2007/12/delivering-mail-to-disabled-accounts.html' title='Delivering Email to Disabled Accounts'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/6092900950976313143'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/6092900950976313143'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-1016106683525243419</id><published>2007-12-28T09:29:00.000-06:00</published><updated>2007-12-28T21:07:38.105-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Terminal Services'/><title type='text'>RDP Connection Manager</title><summary type='text'>If you use terminal services in administration mode for remote access to your servers, you may be aware of a MS tool named Remote Desktops.  Remote Desktops allows you to set up connections for each server and choose them from your connections list.  For those of you that shy away from the command line, it even has a checkbox on the connection properties to allow you to connect to the console.</summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2007/12/rdp-connection-manager.html' title='RDP Connection Manager'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/1016106683525243419'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/1016106683525243419'/><author><name>J</name></author></entry><entry><id>tag:blogger.com,1999:blog-5167218407419816194.post-3358388210687301436</id><published>2007-12-27T21:23:00.000-06:00</published><updated>2007-12-28T21:03:35.660-06:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Putty'/><title type='text'>Copying PuTTY Saved Sessions</title><summary type='text'>PuTTY stores Saved Session information in the following location of the registry:     HKCU\Software\SimonTatham\PuTTY\Sessions

Note:  Simon Tatham is the author of PuTTY, this is not a user specific reg key.

To copy Saved Sessions from one machine to another, you must export the keys from the registry of the machine were the Saved Sessions were created and import them into the registry of the </summary><link rel='alternate' type='text/html' href='http://warmsummerair.com/blog/2007/12/copying-putty-saved-sessions.html' title='Copying PuTTY Saved Sessions'/><link rel='replies' type='application/atom+xml' href='http://warmsummerair.com/blog/rss.xml' title='Post Comments'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/3358388210687301436'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/5167218407419816194/posts/default/3358388210687301436'/><author><name>J</name></author></entry></feed>