I have SBS2008 with Exchange 2007. It's just a test instance. I have a need to programmatically create admin profiles, and I always get the WSAECONNRESET (0x81002746) error. Here is what I have tried (with a user fbs who is a member of every administrator group you can think of): 1. Given full access to all mailboxes to an account that this an Exchange Organization administrator. I've done it a bunch of ways, and I've also executed these shell scripts: Get-Mailbox -Server "FBSSBS2008" | Add-MailboxPermission -User fbs -AccessRights FullAccess Add-ADPermission -Identity "First Storage Group" -User "fssbs2k8.local\fbs" -ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin 2. Tried all this on a non-admin account as well (some docs said you shouldn't be an admin) 3.In Exchange Management console, recipient configuration, made sure fbs is not hidden from Exchange address lists 4. I noticed that the Microsoft Exchange Information Store service logs on as Local System. I have read that that can cause this error, so I tried to set the service to log on as fbs, but when I do that, I always get this error on startup: "The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0)." Is there a reason the service won't start this way, and is this even the issue? Maybe that's not the right service that creates profiles? On other working servers, this runs as Local System with no issues. I've also tried with the Administrator account, and with all accounts, I've waited 2 hours, rebooted, etc., to get around any caching problems. I don't know what else to try. With SBS2008, I never see any security tabs for users. I'm thinking all of this has to do with SBS2008 and its embedded Exchange 2007. Any ideas on how I can get rid of WSAECONNRESET when trying to create an admin profile? Thanks a lot

I recommend you post this on the SBS forum since it could be that SBS is locked down differently from standard Exchange. http://social.technet.microsoft.com/Forums/en/smallbusinessserver/threads Regarding #4, you shouldn't need to change the login for that service.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Thanks -- I'll do that