Replacing the server was one option I pitched but funds are an issue so we'd just planned to migrate to O365 and move them to Essentials 201x next year.
So your suggestion is to put up a temp server, complete the migration and remove Exchange, then install WMF4 on to the old SBS machine? -----Original Message----- From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On Behalf Of Susan Bradley Sent: Friday, April 8, 2016 12:43 PM To: ntsys...@lists.myitforum.com Subject: Re: [NTSysADM] RE: Azure Active Directory Connect Stand up a temp server. Use an eval of something. I'm assuming you'll be getting rid of the SBS 2008? On 4/8/2016 12:26 PM, Neil Standley wrote: > > Hi all, > > I’m working on a staged SBS 2008/Exchange 07 SP3 to O365 migration for > a customer. > > I’ve read that in order for suggested contacts and auto complete to > work after the migration you need to have directory sync working. So > we’d like to be able to sync their onsite AD with the cloud but am > running in to problems getting Azure Active Directory Connect > installed. It wants Windows Management framework 4 installed, with > powershell 3, but I’m reading that WMF is not recommended on SBS or > Exchange previous to Exchange 2013, where it’s a requirement. > > So my question, what do I do now? > > SBS is the only server in the environment and I don’t think it would > be wise to run the sync tool from a workstation, not that they have a > spare anyways. After the migration I am planning to remove Exchange, > but not immediately, I’d like to wait about 30 days to make sure > everything is working properly. > > So should I install the WMF4 and ignore the warnings, or are there > other options I don’t know about? > > Thanks, > > Neil >
