Don't worry. It's just me.

Andy's Blog

Weekend of blue screen of death, McAfee, and Cisco VPN

Andy Pedisich  October 6 2008 07:40:25 AM
Here's how it went.

I use the Cisco VPN with for about 80% of remote access to clients.  Friday my laptop crashed in what I thought was a random. Windows XP Blue Screen of Death.  Shmikerosoft sent me a post crash reference to their standard "it's the driver's fault" page.  Then the torture began.  It came down to this.
  • Restart laptop
  • Restart VPN
  • Connect to client  - BSOD
  • Cold start laptop
  • Restart VPN
  • Connect to client  - BSOD
  • Uninstall stuff I could research that might be causing it, even though they were installed ages ago including:
  • iTunes moble support
  • iTunes
  • Cold start laptop
  • Restart VPN
  • Connect to client  - BSOD
  • Try to uninstall VPN - BSOD
  • Cold start
  • Go to safe mode
  • Try and uninstall VPN
  • Successful uninstall
  • Restart
  • Install VPN
  • BSOD in the middle of the install
  • VPN is 1/2 way installed, On start menu but nothing works
  • Try to uninstall - VPN not in list
  • Try to uninstall something else (Bonjour)
  • MS Installer says VPN install is suspended, wants to know if I'd like to remove it
  • Suspended install backed out
  • Do a system restore from Sept. 29, 2008
  • Cold start system
  • VPN back on the start menu
  • Start VPN - some graphics missing, but works fine
  • Test by connecting to all clients - everything works
  • Notice that while I am working, McAfee is busy installing new version of AV software
  • NcAfee wants a restart
  • Restart laptop
  • Restart VPN
  • Connect to client - BSOD
I want my weekend back.  
I want my VPN back.  
I want my sanity back.

- Andy

Location: Busy busy busy in the Office

3 system templates that give LocalDomainServers only Designer access

Andrew M Pedisich  October 2 2008 12:37:14 PM

This isn't a big deal, but it might be worth mentioning.

I have a very strong point of view about changing the replica IDs of all system templates on the first server that I upgrade in a domain.  And that is, change them!  Every system template from every release has the same replica ID.  Admin4's rep ID  has been the same forever.

To avoid have a mish mosh of design elements, change the replica IDs.

To avoid upgrading the design of databases on servers that haven't been upgraded yet, change the replica IDs.

Typically, I use Surely Template to change them.  This is an app that's available at http://www.OpenNTF.ORG.  It was put together by Rocky Oliver and several other generous individuals.  I change them on a test server.  Then after I upgrade a production server, but before I re-start it, I replace the default templates with my special ones.

When I last did the upgrade to 8.0.1, I noticed that the application was unable to change the replica IDs of several system templates.  Just now I was preparing some for 8.0.2 upgrades and found the same thing.

ADMIN4.NTF

CERTLOG.NTF

DBA4.NTF

Turns out these three have LocalDomainServers set to Designer.  Manager is reguired by the Surely Template application.

But when you think about it, why shouldn't LocalDomainServers have Manager access to all templates?  No reason not to, is there?

- Andy


Location: On the road

What’s the difference between a stockbroker and a pigeon...

Andy Pedisich  October 1 2008 07:17:29 AM
A pigeon can still make a deposit on a Ferrari.

- Andy

Location: Busy busy busy in the Office