Skip to main content

Procrastinator's Recipe for a Great Project Paper

I'm currently at step 6, and so was born this post.

1. Remove one great idea from brain. Put aside for several weeks.
2. Try really hard to remember what that great idea was. Decide on a different mediocre idea instead and write it down this time.
3. Let the idea simmer until one week before the project is due. Victory will taste sweeter this way.
4. Start preparing project paper. Don't research anything, it just slows you down. Stream of consciousness is most effective. Continue until you run out of thoughts, or approximately 500 words into the paper.
5. Ctrl+A, Delete. Repeat Step 4, that introduction page sucked anyways.
6. Mix 1 part great idea with 9 parts alcohol. Maintain the Balmer Peak for 72 hours and write 30 pages of really awesome sounding techno-babble.
7. Suddenly remember that great idea when you sober up. Repeat step 5 & 6.
8. Remove project paper from hard drive. Serve to reviewers at room temperature and really hope that none of them actually knows what "deep packet inspection" means.
9. Celebrate your success by repeating step 6. Great idea is optional at this point.

That's it. Good luck out there, WGU grads!


Popular posts from this blog

Outlook Credential Prompt When Opening Exchange 2013 Public Folder

After completing an Exchange 2007 > 2013 migration recently, I was left with one issue that was preventing us from stamping the project as a roaring success and moving on:

Outlook 2013 users were sometimes receiving a single pop-up prompt for credentials whenever they opened the Public Folder (we have only one). One. Single. Prompt.

Google was frustratingly unhelpful because searching for "outlook prompts for username and password when opening public folders" or something similar just resulted in a lot of folks who were always getting a pop-up that wouldn't go away. It was usually caused by an authentication failure of some sort.

However, we were in a different boat - Users got the prompt once when they first launchedOutlook and opened their public folders, but after entering it they could continue - authentication worked. Next time they logged in to their PC, it would happen again. Not a show stopper, but it definitely generated its share of support calls.

Repairing Mailbox Corruption in Exchange 2010

I recently got through recovering an SBS 2011 server after Active Directory face-planted in the middle of a workday. When I say recover, I mean I repeated the entire migration, using a cleaned up secondary DC - it was a fun weekend (expect another post about that experience). Although I thought we were in the clear, I got a call from the client about 24 hours after we had verified everything was working. He indicated that his iPhone had suddenly stopped receiving mail in the inbox (calendar, contacts, sent items were still fine) and throws up an error after spinning in circles for a few minutes that it "cannot connect to mail server".

SCEP Policy Update Troubleshooting

Because I'm a glutton for punishment, I recently started rolling out System Center Configuration Manager 2012 R2 SP1 and System Center Endpoint Protection across our VDI environment. There are always some considerations to be made in a pooled desktop / gold image type environment when loading software that uniquely identifies devices, but lucky for me SCCM/SCEP handled this just fine without any tweaking. However, there were some nuances to how SCEP policies are applied that caused some serious hair-pulling before I spotted the issues.