Yes, seen that article thanks.
I didn't realise it was no longer supported by MS. I knew that it was no longer supported on Exchange 2003 - but I thought 2007 was a different matter.
Main Topics
Browse All TopicsWould there be any issues in using Exchange 2007 address list segregation on an SBS 2008 machine?
Any pitfalls we might come across regarding how SBS sets up the domain etc.?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
You may go through this excellent white paper.
http://technet.micro
Ahh I think they may have been refering to this section:
"It is also important to understand that attempting to configure Exchange 2007 as a commercial "hosting" solution is not recommended.
The configuration described in this document is complex in nature, and while it can be effective in smaller environments or in limited scope, it can become very challenging to manage such a configuration as the scope of the deployment increases if automation steps are not implemented. While you can use scripts like those described in this document to automate the provisioning process, you must plan for failures in your automation process when they"
No my setup is not on SBS but I have set this up a user that has 50+ users and they wanted the address lists segregated between their locations.
There is no difference in Active Directory or Exchange (other than the OU's that are created for the SBS Wizards to work) so it's worth noting that if you create OU's in SBS that are different from the standard ones then you will no longer be able to use the SBS wizards to create users.
Ah yes, this is one of my concerns about the wizards. I don't have a problem with not using the wizards, my concern is if another engineer were to try to use the SBS wizards after segregation was setup - could this mess something up?
In the setup I'm looking at it's a total of 150 users over 3 floors - but the customer wants to do it in stages one floor at a time - so I thought one SBS box for each floor might be a good idea.
The wizards in the console will just fail if you setup different OU's so they will not be useable.
I am not sure if there is a way around this, to be honest I didn't spend much time looking.
Are you planning on using 3 SBS boxes on the same network/domain? If so you won't be able to.
SBS is required to hold all 5 FSMO roles and it cannot share them.
I should say that this is linked to another question, which may clarify the situation for others
http://www.experts-exchang
Need to sort out the licensing issues still, regarding SPL etc.
Business Accounts
Answer for Membership
by: demazterPosted on 2009-10-30 at 05:12:51ID: 25702118
I have set it up a couple of times and not experienced any problems.
articles_t utorials/e xchange-se rver- 2007/ migration- deployment /shared-ho sting-exch ange-2007- part1.html
Just a note, it's considered unreliable or too complicated and is no longer supported by Microsoft.
The products are essentially exactly the same Windows 2008 and Exchange 2007 they just have wizards and restrictions with regards to licensing placed on them.
There is a full article here on shared hosting with Exchange 2007: http://www.msexchange.org/