StartUP location

[ptmuldoon]

My office has made things so much "easier" (sarcasm) by moving all employees to using Virtual Machines. As a result, all VM's are now connected to our 'network' at all times.

Granted, we need/rely on a good internet to actually be productive now.

But.... with this new approach, I would like to be able to move certain global Addins to a network folder location.

We are using Office 2013, and I think there are actually 2 StartUp location paths available? I'm still researching, but can you possible add a 3rd location or do I need edit one of them?



I would prefer for each user or VM to still have their default %APPDATA%... path, and to possible point a 2nd to the network.

And I found this article that talks about a 2nd location, but it also says it can't be moved.
http://word.tips.net/T001602_Folder_...r_Add-Ins.html

But I would think possibly a Registry Key change could move this to any folder you want?

I'm off to go experiment

[Charles Kenyon]

You can designate the Word Startup Folder but not the Office one, AFAIK. There is no provision for a third. This link has everything I know about the Startup Folder and has links to other resources.

IMO the startup folder (and contained Global Templates) and Workgroup Templates Folder should be local, not network. There can be a central repository for these files on the network which is updated upon user login. Doing this makes use of laptops more feasible, cuts down on network traffic, and makes updating the shared resources easier.

[ptmuldoon]

Originally Posted by Charles Kenyon

You can designate the Word Startup Folder but not the Office one, AFAIK. There is no provision for a third. This link has everything I know about the Startup Folder and has links to other resources.

IMO the startup folder (and contained Global Templates) and Workgroup Templates Folder should be local, not network. There can be a central repository for these files on the network which is updated upon user login. Doing this makes use of laptops more feasible, cuts down on network traffic, and makes updating the shared resources easier.

I would think/agree its best to to keep the StartUP and Template folders local, and you can push the updates on login.

I plan to speak with my IT group in setting that up in the coming weeks. For us though, everyone now logs into a VM every day, so our laptops are just 'dump terminals'. My IT just pushed a policy to force VM restarts every Friday night which should help ensure any templates are updated as there most users never reboot their VM's anymore!