Undo Exchange POP3 Link?

If you allowed SBS to install Exchange (one of the multiple optional components of SBS), then the proper way to join a computer to a domain IS going to setup Outlook to use that Exchange.

I'm guessing that you don't have Exchange setup to handle your e-mail at this time.  I highly recommend it, and can't imagine wanting to keep messing with POP3 boxes when you have Exchange right there.

I would take go back a step and get Exchange fully up and running.  It sounds like you could really use a book covering the basics of SBS 2003, including working with Exchange.  I highly recommend starting with Harry Breslford's book: http://www.smbnation.com/sbs_2003.htm

All 4 nodes were originally set up by (what I have since discovered) a net guy who was not SBS2003 knwoledgeable.  So, he set the nodes up per his win2k knowledge.  Again, I am not an experienced net admin--especially for sbs2003!

So, I have 3 other nodes that have been functioning (and are currently working) with POP3 email accounts from the workstation and do not, at this time, want to muck with the server and Exchange--unless that is by far the best solution here.

I know what was done originally wass not the right install approach.  However, I just want to get the one rebuilt/reconnected client pc back in order.  And that means getting the client's POP3 email account working again.  This is a short-term solution as this pc is the Executive Directors and has been down for several weeks while the workstation was being rebuilt.

Thanks.  

 

This is a tough call.  I believe that Outlook will continually go back to Exchange as the default as a result of the SBS generated login script.  Can you not just add the POP3 info in addition to the Exchange profile?  

In the long run, you will want to move every body over to Exchange.  There are so many advantages to Exchange over POP3 that I can't imagine anyone not using it.  But it is something you need to have some knowledge on (although not too much with SBS, it's highly automated).  

Try adding the POP3 while leaving Exchange in tact and see how far you get.  Then read the recommended book and make a plan to move everyone to Exchange.  (If you don't want to tackle it yourself, there are plenty of consultants such as myself that your company could outsource the work to).  

Since this is a rebuilt client pc, when I open Outlook on the pc it shows the Wecome... message and then tried to match mailbox names--and then the error occurs.  It goes no further into Outlook.  It does not allow me to get into the email accounts setup of Outlook.

Thanks.

So it's trying to connect the user's mailbox, but the user doesn't have one.  

Here's what I would do in your shoes:
Try to create a new Outlook profile.  With Outlook closed, go to the control panel -> Mail, Show Profiles, Add, setup your POP3 and personal folders the way you normally would.  On the profiles list, make sure you change the default to your new profile.  

Then log the user off and back on, if it tries adding the Exchange Server again, I would disable the login script for that user.  (Open the user's properties from the User screen on Server Management, go to Account and remove the SBS_Login_Script.bat)  That should keep it from auto-adding the Exchange profile (and removing some other SBS features as well).  

That should get you back up and running, the Band-Aid fix.  Getting Exchange up and running should still be your next priority.  

If you goto control panel --> Mail.. open the profile for the user (maybe just the Oulook Profile if no other were set) then you should be able to edit this and it will start the account wizard.

specify to change "view/change existing" and from here drop the exchange and add a pop3.

I am giving you a quick blast of info so IF there is NOT any email on this machine you want to keep (doesnt sound like it as it is a new install) then go ahead.

If not, then make sure you take the necessary precautions to pack up the personal folder before making changes. You can find out their location by looking at the properties within controal panel --> mail ---> profiles etc...

Hope this helps

R

Well...what I need right now is a band-aid fix.  I will be going to the cilent site in a day or so to try the suggestion.

BTW, could I not do step 2 first?  That is, on the server, disable the login script you mention?  And then, at the client pc restart it and then open Outlook?

Conversly, what would I need to do to add the client's mailbox to the server? Is there a simple way to do this w/o getting bogged down (at this time) configuring Exchange?  Also, can I just use Excahnge for this one user, and not the others that are using POP3?  

Yes to most of your questions.  You could just go ahead and disable the script right away...I'm not particulary fond of the idea as it is an essential part of SBS, but in this case you may just need to.  Actually, I'm not 100% sure it's the script that will try to force the Exchange connection, but that's my best guess.

If the user was added to the server properly, the Add User wizard would have automatically created the mailbox.  Since that doesn't seem to be the case, I guess you can try manually doing it.  Not sure if there are any snags to that approach, or if there is a wizard that will do this after the fact.  

To do so, open Active Directory Users and Computers (under Administrative Tools), find the user (SBS would have put it under My Business -> SBS Users, but it if the wizard was not used, could be anywhere).  Right-click the user and choose Exchange Tasks.  Then choose to create an Exchange Mailbox.  

However, having this mailbox could cause a host of other problems if other parts of Exchange are totally messed up.  I could go into some of the potential problems, but that would be a whole lot of typing.  If SBS is installed properly and the wizards are used, it just works.  If not, there's a million settings you have to look at and troubleshoot.

That's why I recommend staying away from Exchange just now until you can confirm that it's setup properly.  But it may work, so if you have the time, you can try creating the mailbox.  Worst case scenario you just delete it again.  

FYI: The client pc has two profiles, one for local logon and one for network logon.  The local logon profile has Outlook 2003 that is active and works with a POP3 email account.  I have backed up the .pst when logged in as local.  When logged in as network profile, the Outlook tries to connect to Exchange.  The pc needs to work when logged on to the network.

I have copied/pasted the local profile pst to the network profile pst, so Outlook on that profile is active.

Not sure is this is more useful info or if it confuses things.

Thanks.  

DanKoster...the user is in MyBusiness -> SBS Users.  Also, when I did look into AD users & groups and did a right-click to choose Exchange Tasks and lo and behold, the client's username was already in the address list (highlighted)!  When I saw this earlier today I stopped proceeding thru the wizard b/c it confused me that the cleint workstation cannot see this mailbox when Outlook is opened.

dklauk,  

You don't have to be an experienced Network Administrator to deploy and manage an SBS.  However, you DO need to follow it's very detailed instruction manual and do things the way it describes, and SBS is intended to be used.

Since this was not done from the beginning, as you are aware, these are just band-aid patches.  More than likely, you will see future problems that will require even more patches which may ultimately cause lots of downtime and lost user productivity.  For instance, what you've done by copying the pst file may work for now... but what happens when an update comes down from Microsoft that may throw a wrench in how you have things configured?  (I don't know the answer to that, and either does anyone else... which is why it's always a good idea to follow a best practices methodology).

I would suspect that Exchange is installed and functioning on the SBS since it's done during the original server installation.  However, if you have not done all of the items on the server's To-Do list, then your server installation was never completely finished.  I wouldn't even consider manually creating an Exchange Mailbox at this point.  But if you need to fix things immediately, and the user's profile works when you log in locally then you should use Windows XP's Files and Settings Transfer Wizard while logged in locally.  Save the transfer file anywhere you like (even on that workstation's C Drive is fine).  Then log in with the user's Domain Account and run the wizard again to restore.  Once this is done, remove or disable the user's local account so that it doesn't get cross-linked.

Once you have things under control, I'd highly suggest that you get a good book to help you understand SBS a bit more, and then undertake a full re-installation so that the users will actually benefit from the IT investment made.  See http://sbsurl.com/list for my recommendations of  books.

Jeff
TechSoEasy

TechSoEasy...

Based on your comments, I decided to step back for a bit and recall the history of this installation.  The server (with sbs2003 pre-installed) and 4 workstations (XP Pro pre-installed) were purchased 18 months ago.  I hired a network consultant to help set up the computers and get the users connected to the net, establish an Interent connection, and configure for POP3 Outlook email accounts at the client level.

As I look back it is clear now that the consultant did not know sbs2003 uniqueness as he did the computer setups and connection to the domain manually.  That is, he created accounts on the server and then on the client workstations.  I recall on the workstations that he went through the typical win2k "member of" setups.  I do not recall him doing any To-Do list setup on the server.

Was that a step he had to overtly skip or would one need to have known that the proper way to do the computer and user setups ws thorugh the To-Do list?

Well, I am where i am at this point with this installation.  You have opened my eyes to what is now a mess.  BTW, I am one who will lean to best practices but when I was totally dependent on the consultant, I just didn't know any better.  Shame on me!

Going forward after I get the POP3 email client working for the short-term...

Kindly, suggest the best approach to doing a "full re-installation?" Where do I start--other than finding a good sbs2003 consultant to do this right, once and for all?


Thanks, TechSoEasy for getting me straightened out re sbs2003 vs. win2k.


       

Yes, I agree with Dan... as you can see by the comment I have on my list of books regarding that one.

Jeff
TechSoEasy

1. Can I tell by looking at the server To-Do list to see if that was ever done 18 months ago?
2. Is it possible to leave the OS as is,  delete users & computers on the server domain and then complete the To-Do list?
3. If #2 is not a valid approach, what is the best way to un-install sbs2003?

Thanks guys.

1.  No, but running each step again is not a problem.  However if user accounts or computer accounts were created without using the wizards, more than likely those objects have not been put into the required default OU's (Users go in MyBusiness\Users\SBSUsers and computers go in MyBusiness\Computers\SBSComputers).  

2.  If the above is true (wrong OU's) then yes, you can delete the users & computers and redo, but if they have email in Exchange you'd need to export that out and if they have data files on the server you'd have to save those as well to import back in.  

3.  Try the above first, because there is no way to "Un-install" SBS2003, just as there is no way to uninstall Windows XP.  You need to reformat and reinstall if it gets to that.

Jeff
TechSoEasy

Response to #1...
The connect wizard was only only for the rebuilt client workstation and, yes, it is in the path/folders you mentioned on the server.  Other users and computers are in the Domain folder (as I recall).

Response to #2...
Users have been set up and using their local POP3 client Outlook since day 1.  The new rebuilt workstation has not used Outlook (since Outlook on the rebuilt workstation says it is looking foran Exchange Mailbox) when logged in to the net.

Response to #3...
So, assuming there is no data on the server for any user accounts can I "move" computer and user objects that where not added using the wizard to the correct SBS2003 folder and then do the To-Do list of tasks?  (You can see where I'm headed here as I do not want to reformat the server--that is the LAST scenario!)

Jeff, it sounds like this "mess" on the server can be reolved w/o a complete reformat/reinstall.

Darold  

The connectcomputer wizard is only half of the process... it has to start with the add-computer wizard (or the add-user wizard which chains into the add-computer one).  But that must have been done anyhow since the rebuilt machine is in the correct OU.  The others obviously weren't.

You can move the objects... but you would then have to run the Change User Permissions wizard to apply the correct template to the user objects.  But your last assessment is probably the best answer.  Whenever I am called in to fix a situation like this, I ONLY consider a reformat and reinstall... because then I know that there won't be issues creeping up every month that cost a lot of time and money to troubleshoot and resolve.  A properly installed and configured SBS has very few problems.  Plus, a properly installed SBS will provide REAL cost savings for the company.  This, of course, is your choice... but if it were me, I wouldn't even mess with the mess.

Jeff
TechSoEasy

This is a WAG but for a temp band-aid fix... what if I moved the rebuilt user and computer from the MyBusiness\Computers\SBSComputers & MyBusiness\Computers\SBSUsers folders to where the other users and computer objects are?  Sems like this would put the server config back to where it was before the client computer crashed and had to be rebuilt.  (Just a WAG.)

Assuming the above is not doable, here's my plan...

1. get the client with the rebuilt computer working when logged on to the net.  This means I will need to move the local profile to the network profile (as you suggested) so that Outlook (in the net profile) does not automatically try to look for its MailBox on the server, as it currently is doing.  This would get this user up-and-running (recall that this user is the Executive Director).

2. leave other user accounts as they are on the server until step #4 is undertaken.

3. find a local sbs2003 consultant to assist me in doing a complete sbs2003 reinstall.

4. schedule the time with the client to reinstall the server.

BTW, the book you recommended is on its way.  I already had an SBS2003 book but ordered this book in addition.

Thanks.

Darold

If all you are trying to do is stop Outlook from getting autoconfigured for the moment, then that's simple.

On the client machine, go to C:\Program Files\Microsoft Windows Small Business Server\Clients and rename the sbsdefault.prf file to sbsdefault.bak.  That should stop the autoconfig of swithcing Outlook back to Exchange.

Otherwise leave things as they are, and then continue on with step 3.

Shoot me an email with a copy of your invoice for the Best Practices Book (email in my profile) and I'll send you an electonic version of it.

Jeff
TechSoEasy

Yes, all I ant to do for the band-aid approach is get the autoconfigre changed.  As for the invoice, I'll get that to you.
I will be going to the client site either later this week or on Saturday morning to do the Outlook thing you suggest.  It may be a few days before I get back to you with the results.


Thanks for your help!!

Jeff.. I am assuming that since the connectcomputer wizard was used for this client workstation that the sbsdefault.prf path and file will be on the client workstation.  Per chance it's not, is there another suggestion to "undo" the setting that looks for Exchange vs. POP3 email when Outlook is opened on the client workstation?

Thanks.

If it's not there, then Outlook isn't getting auto configured.

jeff
TechSoEasy

Jeff...

The first thing I did Saturday was to rename sbsdefault.prf and reboot the client workstation.  Unfortunately, Outlook still opened wanting to check Exchange for the user's mailbox name.  Any other ideas as to how to disconnect the link to Exchange on this client computer?

I then went to the local profile and did the files and settings transfer function.  Logged off and logged on as a net user and did the files and settings transfer function for the net profile.

I tried Outlook again and it still looks to the email server for the mailbox name.

I have been trying to recall the installation process of 18 months ago re whether the To-Do list was used.  I konw the ConnectComputer wizard was not.  Is there a way to check on the serve--maybe folder naming/structure--that would tell me whether the To-Do list was completed?

Also, I have checked out some of the info in the book you recommended and while it covers a ton of Best Practices what I see lacking are a ton of "what to do when this or that fails info."  Also, I would like to see a complementary book(let) that is solely devoted to "post-deployment" how to's on real-life situations like re-joining a crashed computer to the net, joining a new computer when an existing user account already exists, etc.  There probably is such a book and I probably just don't know where to look.

Oh well, I'm learning a lot from this experience with sbs2003.

thanks for the help.

The reason I am asking about how to tell if the To-Do list was engaged (18 months ago) is that it may have been done (by the net consultant I hired) but that the connectcomputer wizard was not (I do recall he did the explicit  'join workgroup/member of' approach for each workstation).

The server is a Dell PowerEdge and the OS was pre-installed.  Question:  at the initial power-up of the server, is the To-Do list automatically presented to deploy the OS for the client site specifics  or must the List be manually engaged?    

Thanks.

A Dell Pre-installed SBS always has things that would need to be completed.  To be honest, I'm not sure if the To-Do list pops up specifically or not because the first thing I do with a Dell Pre-Install is to reformat the hard drive.  I've found that Dell's initial settings aren't always done within the SBS Best Practices realm, and I also prefer to have every one of my installations done the exact same way so that I know where problems might be coming from.

In any event... I think what you are asking is whether or not it's possible to tell if the connectcomputer wizard was run on a specific workstation.  Or have you not even looked at the to-do list?  It's always there in the Server Management Console just under Standard Management in the console's navigation tree.

Jeff
TechSoEasy

Duh, Darold.  After looking the To-Do list over again in more detail I do see that it is broken down into Network and Management tasks.  The latter does the setups for the add printer, computers and users functions.  This tells me that the To-Do list was not run initially since if it was started it would not have made sense to stop when it was time to add computers and users.

Well, I guess I have beaten this horse to death now so I will stop by stating I will go to the client site in a day or so and try your suggestion to delete the Outlook profile and reboot the computer with the sbsdefault.prf file renamed.  Hopefully, Outlook will see itself as looking for a POP3 email accont and not Exchange.  If so, this will give the client the network connectivity needed and will give me a little breathing room to get a plan in place to redo the sever--the right way!

Thanks.

Darold