Are you changing the name of the profile to the name I suggested? I suspect
not.

> -----Original Message-----
> From: Bob Andrews [mailto:[EMAIL PROTECTED]] 
> Sent: Monday, January 28, 2002 11:37 AM
> To: Exchange Discussions
> Subject: RE: Public Folders inaccessible
> 
> 
> PFs were rehomed, but perhaps something went wrong there.  
> They look OK. We're finding that we can create new Outlook 
> profiles for new users on the same machines that had the 
> error, but no luck with new Outlook profiles for old users.  
> We've done screen dumps of the registry settings for a new 
> user and are comparing to settings on an old user.  Maybe 
> we'll find the problem there.
> 
> BTW, we'd decommission old servers with a BFH, but are 
> required to recycle.
> 
> > Sounds like perhaps not all PFs were properly rehomed prior to the 
> > decommissioning of the old server.[1] I bet that if you 
> create a new 
> > outlook profile on their existing machines named 
> > "CompletelyNewProfile" and connect using that you'll find the error 
> > doesn't occur either. If that's the case, then the 
> information about 
> > the old PFs is likely stored in the registry settings for 
> the original 
> > profile... Please don't ask me what they are though.
> > 
> > 
> > [1]Do they hold decommissioning ceremonies for old Exchange servers 
> > similar to the ones they hold for old ships?
> > 
> > Chris
> > --
> > Chris Scharff
> > Senior Sales Engineer
> > MessageOne
> > If you can't measure, you can't manage! 
> > 
> > 
> > > -----Original Message-----
> > > From: Bob Andrews [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, January 28, 2002 8:26 AM
> > > To: Exchange Discussions
> > > Subject: Public Folders inaccessible
> > > 
> > > 
> > > We just replaced an Exchange 5.5 SP3 server with an Exchange
> > > SP4 server.  Both NT4 boxes, operating in a Navy Organization 
> > > that replicates a GAL and Public Folders.  This server runs 
> > > IMS and serves as a bridgehead server for several other 
> > > servers. After the replacement, many users of the downstream 
> > > servers lost access to Public Folders.  They receive "Unable 
> > > to expand folder" and "Profile is not configured" errors.  If 
> > > they delete Outlook and reinstall, no change.  But in most 
> > > cases, if the user is set up on a new machine, Public Folders 
> > > are accessible from that machine.  But if a new user is set 
> > > up on a machine that had been used on another account that 
> > > could not get access to Public Folders, the new user also 
> > > could not access Public Folders. Any thoughts? Bob Andrews US 
> > > Navy [EMAIL PROTECTED]
> > > 
> > > _________________________________________________________________
> > > List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> > > Archives:               http://www.swynk.com/sitesearch/search.asp
> > > To unsubscribe:         mailto:[EMAIL PROTECTED]
> > > Exchange List admin:    [EMAIL PROTECTED]
> > >
> 
> _________________________________________________________________
> List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
> Archives:               http://www.swynk.com/sitesearch/search.asp
> To unsubscribe:         mailto:[EMAIL PROTECTED]
> Exchange List admin:    [EMAIL PROTECTED]
> 

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to