Forum Replies Created
Re: sbs2003 to 2012 Essentials + O365
Pretty much on the right track. I’ve done several of these and basically I go:
Prepare source server
Start cutover migration
Install destination server
Migrate fsmo roles, DNS, DHCP
Watch for ad sync errors here: I’ve quite often had journal wrap errors here, but that’s easy enough to fix: the event log tells you what to do!
Migrate data, third party apps etc.
Switchover mx records to 365 and finish cutover miteration.
You can then manage it from the 2012 essentials console ( password sync etc). Bit more involved if full 2012 rather than essentials, but that’s pretty much it!
Re: Windows Server 2012 Scan Folder
I’ve had this on several occasions with server2012 and on each time it’s been because the scanner device didn’t support the SMB 3 protocol. You can either turn off SMB signing (not recommended) or preferably update the firmware on the scanner device.
Re: Exchange 2010 OAB issue on clients
Hi. As a test you could on an affected workstation delete the .oab files at C:UsersuserAppDataLocalMicrosoftOutlook
Then try downloading again. If it works, then in the the past I’ve used a script to delete the files on all workstations and the process then worked. Can’t offer an explanation as to why it’s affecting all your pc’s but it’s probably worth giving the above a go.May 23, 2014 at 11:09 am in reply to: Unable to access EMC/Shell – Network path not found #389305
Re: Unable to access EMC/Shell – Network path not found
Seen this a few times and the following has worked every time:
Close all MMC/EMC instances before proceeding.
Open Registry Editor (regedit) as the user you run the EMC under.
Look for value NodeStructureSetting.
If it is there, back it up and then remove it.
Re: about exchange 2003 on hyper-v
Remember that exchange 2003 predates hyperv by several years, and is not I don’t think officially supported virtualised. Given that some of the significant changes for exchange 2007 and above were for dramatically reducing disk IOPS, then my gut feeling is that your issue is that exchange 2003 is essentially thrashing the virtual hard disks. Exchange 2003 was never designed with virtualisation in mind, unlike especially exchange 2010 and 2013.
Only way I think you’re going to get round this without upgrading exchange would be to ensure that your underlying disk structure is fast RAID10, ensuring that your OS, mail databases and logs VHD’s are on separate spindles. To be honest a migration may be the path of least resistance. If you go the migration route, note that you can only go to exchange 2010 in a single step co-existence migration.
AndyFebruary 5, 2014 at 4:32 am in reply to: how to virtualize a hard drive connected to Hyper-V #389302
Re: how to virtualize a hard drive connected to Hyper-V
Why not just use disk2vhd from sysinternals to convert it to a vhd?January 19, 2014 at 12:14 am in reply to: outlook web access will not load up – page constantly loading #389300
Re: outlook web access will not load up – page constantly loading
Hi. First thing I would you is check the exchange EWS virtual directories and make sure the internal and external URLS and URI are correct: I can’t post links yet, so search for “set exchange 2010 virtual directories”
If you are still having issues, then you can reset the virtual directories and reconfigure them: search for:
“Exchange 2010 reset virtual directories”
I don’t think a self signed cert would cause this, but I have in general found that SBS is a lot happier with a trusted cert.
Oh and it may be worth running the “connect to the internet” and “fix my network” wizards.
Andy cox MCSE server 2012
Re: Event ID 13508 Ntfrs
Sounds like ntfrs is in a journal wrap condition. Had this happen to me recently in an sbs2003 -sbs2011 migration. Not allowed to post links yet, but google or search techneti for 13508 ntfrs journal wrap