Short version: User has admin rights. Long version: Modelel of the printer is missing, users need to be trained to restart when Vipre or Windows tells them to restart. Instructing them on the consequences of failing to do the restart when requested is just as important. Lastly, employees should not allow IT people not from your company to touch the laptop. You have no idea of what he did, and even if he told you what he did, he likely forgot something unless he was taking notes while he was doing it.
There's a huge black hole of missing information that can only be filled in by speculation, or someone who has the same exact printer and also underwent the vipre upgrade and proceeded to ignore the restart warning that it is unlikely you'll have a (satisfactory) answer. On Mon, May 10, 2010 at 9:11 AM, John Aldrich <[email protected]>wrote: > Here’s the situation: > > I have a few laptops that I manage running XP Pro SP3. Last night (Sunday) > one of my users called me at home saying he had been working on an important > presentation and when he went to print it, he realized he didn’t have his > home printer installed, so he tried to hook up an old HP Inkjet he had at > home. Then after installing the drivers, Windows said it needed to reboot > and when he did, it all went south. The laptop would not let him log back in > as it did not recognize his USERID and a friend of his (an IT Manager for a > big telecom company which shall not be revealed) poked around and couldn’t > find his profile (on the d: drive) so they called me. > > > > I drove an hour into the office to meet him and I found the same thing. It > wouldn’t even recognize **my** profile. It gave me an error when I tried > to log in that a Google search turned up a Microsoft article about too many > security products installed. The error was 0x00000035 > NO_MORE_IRP_STACK_LOCATIONS. The article gave a registry hack that should > fix it if a hotfix was applied, prior to SP3. The same article stated that > the hotfix was included in SP3, but it also said that if the hotfix was not > installed, the registry hack would be ignored. > > > > It **did** allow me to log in as the local admin in safe mode, but would > not let me log onto a domain account, even after the registry hack. I was > also unable to pull up the installed programs list (add/remove programs) as > the local admin in safe mode. I ended up wiping and reinstalling Windows. > Office and Vipre Enterprise. I also had to format the D: drive as Windows > said it was not formatted. > > > > Now one thing I haven’t mentioned until now was that I had upgraded Vipre > Enterprise from Vipre 3.x to Vipre 4 the previous week, and advised the user > to restart his computer. He never got around to restarting it until Sunday > evening after installing the HP printer driver. > > > > Any clue what could have happened? > > > > [image: John-Aldrich][image: Tile-Tools] > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
<<image001.jpg>>
<<image002.jpg>>
