Two posts in one day! (aka fun w/ MS Office)

OK, so now for my second post in one day (insert fireworks here!!!) I will be attempting to stop MS Office from running the Windows Installer when a network user access' the software for the first time. Currently when an AD user logs in to a system and o[ens up MS Word (or any other Office App) for the first time it wants to do the installer and prep for first use stuff. I'm not really sure how to disable this (can I? doesn't the software need to get your username, etc.?) but one thought I've had is to see if I can pass a -s (silent) parameter somewhere along the line or perhaps clone the generic user info? Well . . . here goes nothing!

 

Getting back into this thing (maybe?)

So, this blog is pretty sparse (OK, really sparse) but I'm gonna try and get myself functioning on a bit more of a functional level now and actually post stuff, who knows, maybe I'll learn something in the process!!!

So for today's fun and excitement I will be attempting to convince a WinTel machine to not create a new user profile every time a new network user logs on. First thing to try is to remove the "STUBPATH" registry entry based on advice from Mr Gates himself (http://support.microsoft.com/kb/238441) . . . & wow - it actually seems to have worked! Now when a user logs in on a new (or re imaged) system we don't have to wait while it runs all the personalized settings stuff.

Now let's see if I can convince the machine to not run the Windows Installer on MS Office when a user opens it for the first time . . .

OK, so I've tried a zillion different registry hacks to no avail, now just gonna nuke it and reinstall (uninstall, run ccleaner to clean registry, reinstall as a domain admin with all options set to run from computer) and see what happens, fingers crossed and . . .

Didn't work, feel free to leave me any suggestions (as if anyone but me is gonna read this!) below and I'm out for the weekend, have a good one.

SC