rundll32 zipfldr.dll,RegisterSendto

In the background, a zero byte file named Compressed (zipped) Folder.ZFSendToTarget will automatically be created in the %Userprofile%\SendTo folder.  This command works for both Windows Server 2003 and Windows XP.

For Windows Vista users the fix is similar but the command is different.  The Compressed (zipped) Folder icon is present in each user profile and also in the Default user profile. Follow these steps to restore the icon to your user account:

1. Click Start, type the following where it says "Start Search" and press Enter (case sensitive):

%systemdrive%\Users\Default\AppData\Roaming\Microsoft\Windows\SendTo

2. Right-click Compressed (zipped) Folder and choose Copy (Shortcut: CTRL+C)

3. Open the SendTo folder of your user profile. To do so, click Start, type the following and press Enter:

shell:sendto

4. Right-click an empty area in the folder, and choose Paste (Shortcut: CTRL+V)

Happy Zipping!

I did a little research on what the NET command can do by opening a DOS prompt and typing 'net /?' and pressing Enter.  This showed me all the options available for the NET command such as NET USE for mapping resources and NET TIME for setting a computer's time.  The syntax I used is as follows:

net localgroup administrators %username% /delete

Using 'net localgroup' tells the computer I am going to reference items found in local groups on the local computer, meaning the computer on which the command is being executed.  Adding 'adminsitrators' to that string means I am looking specfically in the local administrators group.  I used the variable %username% to insert the currently logged in user into the string and the used the /delete switch to delete that user.  Final result?  The currently logged in user is deleted from the local administrators group.  This can be verified by using 'net localgroup adminsitrators' to print out a list of users in the local administrators group.

Since I didn't want each user to have to execute this command personally I created a batch file called removeadmin.bat which contained the command as seen above: net localgroup administrators %username% /delete.  I then added this as a logon script in a Group Policy that was applied to the OU containing the users.  In this way I was able to make the script run after login and remove the current user from the administrators group with relative ease.

See http://support.microsoft.com/kb/556003 to learn more about the NET command.

For physical installation of the devices I relied on the my client's maintenance staff.  The EOC-2610 comes with a hose clamp style mounting system that easily clamped on to a custom bracket that was attached to each building.  Power and network connection are delivered to the devices via their PoE interface.  The PoE injector and A/C adapter are included with the devices.  Since they were mounted outdoors, I used direct burial Category 6 ethernet cable to reach the devices.  Once the cable came inside the building I terminated it and continued to the indoor switches with standard Category 5e cable.

Implementation was fairly painless once I deduced the appropriate operating mode for the devices.  The devices can be configured via web console in 4 modes: Access Point, Client Bridge, WDS Bridge and Client Router.  For the main building I chose Access Point (AP) and for the remote building I chose Client Bridge.  Once this was done I created a wireless network on the Access Point and enabled WPA2-PSK/TKIP security.  To connect the AP and the bridge I logged into the web console on the bridge and all I had to do was scan for networks.  Once it found the network I wanted (and it found a bunch!) I could then connect with the appropriate passphrase (set from the AP's wireless config). In the remote building I installed a 24 port switch that receives the up-link from the bridge and then allows me to operate wired PC's and printers within the remote building.

So far I am very satisfied with this solution.  The EnGenius website says this device can transmit up to 30km or 18+ miles.  I am not sure about the total range, but it does work great for the distance I needed to cover.

Pros:
-Easy installation/configuration
-Long range and strong signal
-Cost effective

Cons:
- I would like to have had a MAC filtering option so that I could limit the devices that can connect to this signal (limiting wardriving)

Project Pictures:

Remote building device

Main building device

Backside of main building device, showing mounting bracket

Relevant system details:
Windows XP Pro SP3 (OEM installed)
Internet Explorer 8 version: 8.0.6001.18702
Adobe Reader 9.3.0

I spoke with the Ameripath's support team and they initially told me that the application was not supported in IE versions later than 6!  However, after further investigation, I received a call back and I was informed that an upgrade had added support for IE7, 8 and Windows Vista/7.  This meant there was something wrong with the laptop in question.  After successfully testing the Ameripath application on my own laptop (XP Pro SP3, IE8, Adobe 9.3.1)  and successfully testing the application on the Ameripath tech's system (SP3, IE8, Adobe 9.2) I was lost as to why this new laptop was causing me problems.

Other steps taken:
-reset IE8 to full defaults
-disabled all IE8 add-ons/extensions

When tweaking settings in IE and Adobe didn't help I decided to fully uninstall Acrobat 9.3.0 and reinstall it.  After I uninstalled Acrobat 9.3.0 I changed my mind and installed 8.2.0 instead.  I found the MSI for this at this link. Once I had Reader 8.2.0 I launched the Ameripath web application and to my great surprise it worked flawlessly!  Thinking that maybe the initial 9.3.0 install had been damaged, I upgraded from 8.2.0 to the 9.3.1 package.  After restarting and retrying the application IE8 again froze when viewing the PDF report.  I also considered uninstalling IE8 but was not able to do this because it was installed as part of SP3 at Dell.  I wanted to roll back SP3 as well but found no efficient way to do that either.

So... the final fix for this issue?  Uninstall Reader 9.3.0 and install 8.2.0.  I haven't tried incrementally upgrading to see how close to version 9 that I can get.  I just don't have the time or the patience to do that!  I cannot determine why the Ameripath application works with IE8 and Acrobat 9.3.1 on my system but does not work on the client's system.  The only difference is that the client's system had OEM installs of Windows XP, SP3 and IE8.  My system has been slowly updated over the years as these updates have come out.