/build/static/layout/Breadcrumb_cap_w.png

Normal.dot change in users APPDATA folder

Hello folks,

I know it's a long post but please hang in there!

At present I have been tasked with a simple application that amends the Normal.dot template used in Microsoft Word. - SIMPLE? Read on............

The Normal.dot file is located at "C:\Documents and Settings\<username>\Application Data\Microsoft\Templates" and everytime a new user logs on the Normal.dot file gets copied to their local profile "C:\Documents and Settings\<username>\Application Data\Microsoft\Templates" which will in turn get copied with their Roaming profile - I presume.

Installing app as local admin!
Firstly the Normal.dot file in local admin's account gets overwritten with the new Normal.dot that I've created.

When Word is run, the toolbar appears - OK, the application works.

Then log in as Roaming User account.

Run Microsoft Word, it will have the toolbar present as it will have self-repaired on install (active setup) and copied the New Normal.dot (the one I've created) to it's profile in "C:\Documents and Settings\CPDDtest200\Application Data\Microsoft\Templates".

That's all fine, the application works fine.

BUT..........On Uninstall...........

When I then uninstall the application logged on as local admin the Normal.dot file only gets deleted from the local admin account and not from all of the users that have logged onto the machine. Therefore, after the app has been uninstalled a user will still log on and have the old Normal.dot (the one I created) file present, and therefore the Toolbar will be present.

Also, after uninstall as local admin, the Normal.dot file gets removed completely leaving the C:\Documents and Settings\<username>\Application Data\Microsoft\Templates directory empty. When you then run Word after Uninstall, Word creates it's own "new" Normal.dot file and Word works fine.

However, my worry is this - What if my Core build has a customised Normal.dot file? Has anything added to the Normal.dot file that Microsoft provide? If so, this could be a potential hazard as when I remove my package I am in turn removing whatever customisations the business have made to the Normal.dot file. - My Worry.

It is possible to Uninstall the Normal.dot file from the machine completely, by writing a script that searches through every users local profile for Normal.dot in C:\Documents and Settings\<username>\Application Data\Microsoft\Templates and deletes it.

But..........another but...........Another potential problem will be roaming profiles!!!

If I uninstall the Normal.dot file from the local machine, i.e. every users local profile. Will they then get the Roaming Profile copied to their machine when they log on and get the incorrect Normal.dot file? I think they will.

Anyone ever do anything like this?

0 Comments   [ + ] Show comments

Answers (2)

Posted by: nheim 17 years ago
10th Degree Black Belt
0
Hi Mark,
have looked up the possibility to create a global template?
Have a look here: http://addbalance.com/usersguide/templates.htm#Global
Regards, Nick
Posted by: mark_holland21 17 years ago
Fourth Degree Green Belt
0
Hi,

Thanks for your reply.

That might do it actually. If I just put the template in question in the C:\Documents and Settings\<Username>\Application Data\Microsoft\Word\STARTUP folder then it should open everytime someone runs Word.

I should then be able to remove it without affecting the Normal.dot template!

Thanks a million, I'll go and give it a go!
Uninstall and the roaming profile could still be an issue but at least this is better than editing the Normal.dot template!

Thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ