Skip to main content

Server 2016: Role Tide (Or; Exporting Server Roles to A New Server)


You don’t want to “upgrade” a server. Everything’s got history, you, me, and technology, despite companies’ best attempts to even physically scrub encoded data off of machines.

And maybe it’s not compatible with the older hardware.

So, here’s role migration — Role onto a new server, with all the configuration of the old one.




The video is transferring a DHCP server (With configurations!), and unfortunately we don’t have a second server to manipulate, so we’ll put in the commands after we read what happens here and go as far as we can.

 I could take screenshots from the video but that’s not real learning.

Of course, both servers should be on the same network.

First, let’s install the Windows Server Migration Tool from Add Roles and, specifically, Features.

You tell the old server to export the configuration in a way humans can understand.

On the target server, open an Elevated Command Prompt.

cd %windir%\System32\ServerMigrationTools

Takes us to the appropriate directory.

Then run

smigdeploy.exe /package /architecture amd64 /os WS12R2 /path c:\smigtool12r2

RIGHT SO what does all that mean?

the architecture bit has to match that of the processor the source server used.

the os is the operating system. Windows Server 2012 R2

the path and subsequent c: is where the tool will run.

Hit enter, open the file browser, navigate to the appropriate drive, and there it is!



(there’s so much stuff!)

Now to get it onto the source server. Stick it on a flash drive.

After a quick rename, the elevated command prompt comes back and we move to cd \smug

Running the executable (dir *.exe, because * = wildcard), there are only two executables, so let’s run smig deploy.

And welcome to a Powershell enviroment, specially built so we can run waht we need.

Verify the roles to migrate -

Get-SmigServerFeature

(You can’t export a running service)

Export-SmigServerSetting -FeatureID DHCP -path c:\WhereAmIGoing

Despite exporting it to the new server, you do have to add the Role.

In the post install window, it’s trying to import, and it may not have finished authorizing the DHCP server. Ok. It’s fine.

Under tools, go to Window Server Migration Tools, pull up the terminal:

Import-SmigServerSetting -FeatureID DHCP -Path c:\WhereItWent -force





Comments

Popular posts from this blog

What Do You Need? [AKA; List of Offered Services / My Next Role] (2020)

UPDATED 2021 I am a trusted outsourced remote consultant for your company.   I enjoy having the flexibility to take on temporary projects from time to time! I start at part-time, temp work for now. If we like each other, we can renegotiate. If anything sounds weird, out there, or unusual - Feel free to e-mail me .  3 Services Offered Technical: Cloud Technician     Azure [ See tag ] WORKING ON: Infrastructure As Code (Specifically Terraform/Azure and CloudFormation/AWS)  Support [Web: Example Job Description ] [Text : Example Description ]     I help you with adjustments in HTML, CSS, and Javascript.     When you email a business a question and they answer? That's me.   IT Operations Tech [ Example Job Description ]     Hardware and SaaS support.     Cisco routing and switching (Networking). CCNA, A+, Sec+, Azure certified WORKING ON: Junos Networking  Writing :      You want to pay me to write more of *waves hand* this blog? I am game .     I write B2C e-mails going out to o

Contactless Tech’s Role in the New Guest Experience ft. Intelity and The George

 Contactless hospitality technology is growing. You want to get away, and you'll be damned if a little thing like a deadly virus will stop you! But you still don't want to touch things. Ew. During the chat between INTELITY CEO Robert Stevenson and THE GEORGE Director of Operations Kerrie Hunter, you’ll learn how the historic boutique hotel has adapted a mobile-first guest experience in the wake of COVID-19—and how they see contactless technology affecting the future of hospitality. I don't remember how I found INTELITY (probably hoping to score a position with them), but I liked them enough to stay on the e-mail lists.  

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H