I was following through the migration guide for SBS2011 to Server 2019 ( https://server-essentials.com/support/migrate-sbs-2011-to-windows-server-2019# ) and then under Section 7 Step 21 is to verify that there is a SYSVOL and NETLOGON share on the 2019 server and unfortunately they are not there. How do I resolve this to continue the migration? Thanks for your help.
Hi, I'm about to buy your migration kit to support me on this migration in a customer's site. My doubt is about which kit I should purchase considering that I will only migrate the DC because Exchange is not already running there. They also have user profiles redirected to a WS2008 file server in the Domain, which I want to break and revert them to the workstations. So, does the SBS2001 Essentials (€199) kit will be enough or, do I have to purchase any of the SBS2011 Standard kits? thanks in advance
https://server-essentials.com/support/cutover-migration-sbs2011-exchange-server-2010-to-office-365 I am trying to run the script on SBS2011 Get-Mailbox –ResultSize unlimited –Filter {(RecipientTypeDetails -eq 'UserMailbox')} | Add-MailboxPermission -User 'migadmin' -AccessRights FullAccess -InheritanceType all And I am getting: User or group "migadmin" wasn't found. Please make sure you've typed it correctly. + CategoryInfo : InvalidData: (:) [Add-MailboxPermission], ManagementObjectNotFoundException + FullyQualifiedErrorId : 4AE421D1,Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission What am I missing.
OK , So after following the migration document the system seems to have stalled .. Running the PS script $currentDomain = Read-Host -Prompt "Enter your internal domain name" $cred = Get-Credential -Message "Enter Domain Administrator Credentials" Install-ADDSDomainController -NoGlobalCatalog:$false -CreateDnsDelegation:$false -CriticalReplicationOnly:$false -DatabasePath "C:\Windows\NTDS" -DomainName $currentDomain -InstallDns:$true -LogPath "C:\Windows\NTDS" -NoRebootOnCompletion:$true -SysvolPath "C:\Windows\SYSVOL" -credential $cred -Force:$true -Confirm:$false -SafeModeAdministratorPassword (ConvertTo-SecureString 'xxxxxxxxxxxxxxxxxx' -AsPlainText -Force) *Password adjusted for this thread It accepts the details and no errors are generated ( warnings yes) Started doing something then has stopped , the migration document suggests that it reports as ...
Nearing the end of migration and running into an error trying to install the Windows Server Migration feature on the old 2016 server. Install went fine on the new server. Attaching images of the error. Is there a way around this without too much work?
Step 9 - Migration tool installed on 2019 but error on 2016. Same error as here - https://server-essentials.com/community/answers/migration-tool-install-failure# - HP server with HP media. Saw references to cbs.log like this answer - https://server-essentials.com/community/answers/unable-to-install-windows-migration-tool-on-windows-server-2016 which isn't quite the error I have. I do have 'failed to pin' deployment for KB5036899 and KB4524152 in the cbs.log. I downloaded 5036899, extracted and installed with dsim cmd was supposedly successful. Tried to install Migration Tool had same error. 4524152 is old and not available to manually download that I can find. I won't be able to restart the server until this evening. ...
Hi, following the tutorial to install a Hyper-V Core Server 2012/2016 ( Install and configure RSAT on Windows 10 and make it a management workstation that connects to a Hyper-V 2016 core server in a workgroup ) I got a problem when trying to edit the RSAT via DCOMCNFG as Admin: there are no "Properties" under MyComputer selectable. So i can't set the anonymous login as suggested (Steps 4-6). Any ideas how to fix ? RSAT Client is running Win10 64 Pro 1809 in a Workgroup, tried also with Client in in AD - but same situation. EventMgr ...
While trying to migrate mapped drives from SBS2008 to Server2016, I find no Windows SBS Drive Mapping Policy to edit in GPM on the old or new server. I'm concerned about moving forward if the drive mappings on the users break. Any ideas please? Thanks, Mike
I have WSE 2016(server name = WSE2016) installed in a VM and Exchange 2016 (server name = ExchSrv) installed on another VM. Exchange OWA works when ports are forwarded to EchSrv. Access Anywhere works when ports are forwarded to the WSE2016 machine. Since both use 80/443 I have to pick one or the other to publish externally. Unless I can merge them into the same IIS server. From what I read, moving QWA to WSE2016 isn't going to work so I am curious if Access Anywhere can move to the IIS on ExchSrv. Or, if I am missing ...
I got a little carried away and moved the FSMO roles to my new server. Can I move them back to the SBS 2011 and thereby stop its countdown?
Hi everyone, Getting a warning when selecting arbritation mailboxes to move to Exchange 2016 (from Exchange 2010 SBS 2011): The object domain.local/Microsoft Exchange System Objects/SystemMailbox{746E229B-0847-44FE-A23B-A2F68E467C25} has been corrupted or isn't compatible with Microsoft support requirements, and it's in an inconsistent state. The following validation errors happened: Database is mandatory on UserMailbox. ???
Hi! I am on the final step before demoting the SBS! I'm checking my CA on the SBS and I can see that the root CA expired in 2019, oops! Now, this hasn't caused any issues up to now but what are the chances that I could run in to an issue when attempting to restore onto the new WS2019 DC? Will it self generate a new root certificate when I restore the backup to the new server? I'm confident it will work fine but wanted to ask the question :) Thank you
Hi, I am looking for documentation for moving Windows 10 Pro and Enterprise computers from Windows Server 2012 Essentials and joining to new installation of Windows Server Standard 2019. The 2012 server will be in use at an old location; user's workstations will be moved from the old location to a new location with Windows Server Standard 2019 installed. Do user profiles have to be rebuilt to join to the new server? Or what is the process for unjoining the old domain and joining the new domain. Thanks! Bev S
Hello - I am in the middle of a migration from SBS2011 to Exchange 2016 using your guide. I am at Step 11 - Move User Mailboxes to Exchange 2016. The default location for the Exch 2016 mailbox is on C. I need to move this to another drive before moving mailboxes because I will run out of room on the C drive. Any problem doing this at this point? Do I just change the mailbox database path in the database settings? Thanks!
Hi, Quick question: SBS2008 Exchange 2007 to Exchange 2013 - If I don't use Public Folders do I have to do step 11. Migrate Public folders ? I have moved the user mailboxes but not Public (yet) when I start Outlook on the client it prompts for Credentials, but I think that is for the existing Public Folders that are still on the SBS2008 (as normal mailbox working OK and receiving email), but clicking on the Public Folder for that mailbox gives the can't access error. If I do not migrate them will they disappear in Outlook ...
I need to replace an SBS 2011 Essentials server with a 2016 Essentials server. The workstations were connected to the domain using the Connector and are currently backing up to the SBS 2011 Server. Is it possible to move those backups (about a month's worth) to the 2016 Server? If so, is that covered in the " How to migrate from SBS 2011 Essentials to Windows Server 2016 Essentials" guide? Thanks.
The available guide goes to MS Server 2019 Standard. Does anyone know if I can use that guide to move directly to Server 2022 Standard? Thanks, Paul
Hello Mariette, I have purchased SBS2011 with Office 365 Kit and SBS2011 with Exchange Kit, but did not find any info about this configuration there. I have a client running one SBS2011 with emails for three different web domains. abc.com for 5 users, 123.com for 2 users and 1234.com for another 5 users on the same SBS2011 system. Do you have any guidance for Migrating the three domains to a new Exchange 2016? Thanks for your help. Love your kits! Best Regards, -AJh
Hello Mariette, Thanks for your response, I didn't ask the right question. This is in regard to Migrating Exchange 2010 from SBS2011 to Exchange 2016 running on Server 2016 locally: I have purchased SBS2011 with Office 365 Kit and SBS2011 with Exchange Kit, but did not find any info about this configuration there. I have a client running one SBS2011 with emails for three different web domains. abc.com for 5 users, 123.com for 2 users and 1234.com for another 5 users on the same SBS2011 system. Migrating to Server 2016 DC and Server 2016 with Exchange 2016. ...
if I have multiple WSE2016 server in multiple branch office (with BranchCache activated as Hosted Cache) is it possible migrate only one of those to w2019? Is there BranchCache in 2019?
My challenge is to migrate from a old SBSe 2011 server platform used in a heavy AutoCAD (LOB) environment, where most every AutoCAD project has large numbers of embedded UNC server-based file references. In the past, I used Jeff Middleton's Swing Migration, which used a temporary secondary domain controller to transfer Active Directory from the SBS server and then used a THIRD (final target) server running then then-latest version of Windows Server Standard bearing the original SBSe server's name. My goal is to migrate the SBSe 2011 SYSTEM (Drive C: with Windows, AD, DNS, Redirected folders, etc.) and ...
A few months ago, I completed a customer's 2022 server migration to 2025 utilizing your migration guide to keep the same hostname. The client let me know this week that a workstation is having issues and running very slowly. Looking at the event viewer, I see the error from NetBT complaining that the name SANDTENT could not be registered. The IP 192.168.111.101 is the workstation, and 192.168.111.20 is the server (named PDC). I log into the server and see a similar error in the event logs there as well. SANDTENT has never been a workstation or server name; ...
Hi, I have a Windows Server Essentials 2016 Network at home with several Clients (All win 10 x64 professional, current Patchlevel, the problem occurs on ver 1809 as well as on 1903. I have my DNS set up on my server, works fine. The local DNS is being propagated on the network by my router, so all clients are on autodetection of DNS and find my DNS correctly, A single client suddenly started to set the DNS as if it was set manually in the network adapter options under Ipv4 and Ipv6. This resulted in the network ...
I recently completed an SBS 2011 Standard to Server 2019 Hyper-V/Exchange 365 migration using the SBS Essentials guide. All went well with no problems except that after a reboot of the Hyper-V host network adapters on the Hyper-V host and guest servers is switching to "Private" from "Domain". This causes login problems to the file/print and application guest servers. Hyper-V setup is: IT-HYV Hyper-V Host IT-AD ASD domain controller IT-Landtech application server IT- Poweredge1500 file/print server All servers are joined to the domain. DNS is setup ...
I am preparing for an SBS2011 to WS2016 Essentials Migration We are using a cutover migration to O365. Following the cutover, what will be the client\workstation experience with Outlook? I need to explain to clients what to expect. Do we need to remove the original Outlook Profile and associated OST.