To do list for swapping computer

A quick to do list for swapping laptops:

On the old laptop:

1. Gather all data from the previous laptop including (but not limited to):
   a. desktop
   b. documents
   c. favorites
   d. Firefox profile data
   e. Chrome profile data
   f. music
   g. pictures
   h. videos
   i. Outlook NK2 file
   j. Outlook archive (check both c:\archive and the folder in appdata\local)
2. Gather profile info from previous computer including (but not limited to):
   a. default printer
   b. default browser
   c. additional mailboxes open in Outlook
3. Note any additional nonstandard programs that may be on the laptop including (but not limited to)
   a. Dropbox
   b. itunes
   c. Acrobat, Photoshop
   d. NitroPDF
   e. Skype
   f. Google Talk
   

On the new laptop:

1. Log in as the user
2. Configure Outlook as needed including (but not limited to):
   a. configure account
   b. configure archiving as appropriate
   c. add bcc field to new messagee
   d. copy signature from sent items to this Outlook
   e. add back any additional mailboxes to Outlook
3. copy data from backed up data from old laptop including (but not limited to):
   a. desktop
   b. documents
   c. favorites
   f. music
   g. pictures
   h. videos
   i. Outlook NK2 file
4. add all relevant printers
5. set proper default printer
6. install browsers, if needed
7. copy Chrome/Firefox profile settings to new computer 
8. set proper default browser
9. add terminal server icon to desktop (if applicable)
10. set up VPN and/or add icon to desktop (if applicable)
11. install TightVNC (if applicable)
12. Rename computer with appropriate initials in computer name
13. set up backup
14. install all updates
15. make sure antivirus is up to date
16. track new computer ownership in inventory spreadsheet

Fixing Unifi errors on 64 bit systems

I've become a big fan of Ubiquity Unifi wireless devices (with the exception of the absurd fact that their standard devices support wireless speeds of 300 Mbps but only put in a 100 Mbps ethernet port - real genius there).

If installing the controller software on a 64 bit machine, I found these tips to help the Unifi controller work better from their forums:

If you are getting an error when double-clicking the shortcut saying that the that the javaw.exe executable cannot be found -- then -- be advised the default installation on the 64 bit platform creates the shortcut incorrectly. Repoint the shortcut from ..\system32\.. to ..\sysWOW64\..

Or if the controller tries to start and then can't, complaining about port 8080 being in use, first simply try logging off as that user and logging right back in (do not reboot).

forwarding email with autoreply on Office 365

One of my clients' preferred way to handle a departed employee is to set up an autoreply and forward the email to another staff member.  This doesn't work as it should on Office 365.  With a regular on-premise Exchange server, you can set up the autoreply in the mailbox and configure forwarding with still delivering the message to the departed user's mailbox, and it works as intended.

With Office 365, the forwading happens, but the autoreply doesn't go out even though the mailbox is configured to receive the message.  Very annoying.

To get around this, I had to configure the autoreply and set up an Outlook rule to forward the messages.

While researching this, I found this semi-helpful page on dealing with terminated employees when you have Office 365:
https://www.cogmotive.com/blog/office-365-tips/dealing-with-terminated-employees-in-office-365

Xerox printers disappear and cannot be reinstalled - print processor trouble

I had two client computers over the course of a week have two copiers disappear from their list of printers.  All of other printers remained.  And when I tried to re-add the printers - whether via the printer server or as local IP printers, it would fail.  It was isolated to my two Xerox printers.

I don't remember where I found it, but I found a reference to a problem with the print processor.  The print processor is isolated to each model of printer.  In the end, I have to delete the print processor data from the registry for Xerox printers and then reboot.  Problem resolved.  Of note - these machines were each infected with malware the week prior.  Several days passed between the infection and the issue - so I can't draw a correlation, but just to note.

Here's the registry entry I had to delete:

uninstalling GP Dynamics 2010

I had some trouble uninstalled a broken GP Dynamics 2010 install - so I thought I'd document what resources I used to do the uninstall:

http://www.kuntzconsulting.ca/index.php/blog/article/issues_with_gp2010_and_uninstalling

and

http://support.microsoft.com/kb/2581260