Originally when we deployed Outlook 2003, we pointed to say the front-end
server "A." Meanwhile 9 months' later, they determined they forgot to check
the box that stated front end, now our configuration for "A" does not
resolve, but we need to check everyone to "B." So we utilized the custom
maintenance wizard to push the changes along with the change for add the
Outlook Address Book. We also updated out MST file with these parameters and
new machines are wonderfully working. The machines that multiple folks log
into, we run the custom maintenance wizard that creates the custom11.prf file
under c:\program files\microsoft Office. Partners are complaining they are
losing their signatures and other settings and we note there is the Backup of
%username% in profiles, something 3-4 times.
The norm is mulitple people logging into one machine and sharing the
machine. So we run the profile wizard, which resolves the server "B" just
for the person. Someone logs onto that machine that had already logged on
before and they are not fixed, but still pointing to server "A." A new
person logs onto the machine and thye are correct and have server "B." Point
being, how do we fix the existing profiles or do we need to run the
maintenance wizard for all folks logging into the machine? Lastly we know to
edit the prf file and turn off BACKUPPROFILE=NO, but is there somewhere in
the Custom maintenance wizard when configuring this fix to turn this off.
Otherwise we need to edit this file on each machine to place that
configuration in there.
Any help would be greatly appreciated.
|
Similar Threads
