Moving AD Operations Master Roles

To find your PDC you need to use PowerShell. First, run:
netdom query FSMO

to gather the information. You should see similar to this:

Schema Master DC1.domain.com
Domain Naming Master DC1.domain.com
PDC DC1.domain.com
RID pool manager DC1.domain.com
Infrastructure master DC1.domain.com

Since we want the roles on DC2.domain.com, we need to run this PowerShell command:
Move-ADDirectoryServerOperationMasterRole -identity "DC2" -OperationMasterRole 0,1,2,3,4

The 0,1,2,3,4 are numeric representations of each role to move.

Now, if you run netdom query FSMO again, you should see this output.

Schema Master DC2.domain.com
Domain Naming Master DC2.domain.com
PDC DC2.domain.com
RID pool manager DC2.domain.com
Infrastructure master DC2.domain.com
Advertisements

70-410, My Opinion

Since I recently blogged about studying for the 70-410 Installing and Configuring Windows Server 2012 (R2) I’ve decided to give my opinion about the exam. Granted I hardly passed, I feel that the test was slightly unfair. In my opinion the exam was well written, some questions a little extreme, and there was stuff on it that actually wasn’t covered in the reading/videos I watched.

So, what can I do about the stuff that I felt wasn’t in the material? Nothing. But, I have heard that you will be best suited to study for the 70-410, 70-411 & 70-412 THEN take all 3 tests individually. Some material bleeds over into the next study material. Now I’m moving onto the 40-411 and fully plan to study for the 70-412 before taking it.

If you are planning on taking any of them, good luck!

How to Install .Net Framework 3.5 on Server 2012 R2 with PowerShell

Recently, I noticed that installing .Net Framework on Server 2012 R2 is not very straightforward. When I got the below error I started looking around.

GUI Error

I found this blog, which does a beyond great job demonstrating utilizing the GUI. However, if you want to use PowerShell or don’t have a GUI (I don’t know if you can install .Net w/o a GUI though), I found the commands to do so.

In order to verify 100% that the service did not install when I tried with the GUI, I restart the computer, then ran:

Get-WindowsFeature -ComputerName VM *NET*

and got the following results.

Feature Install

Since the Role of “.Net Framework 3.5 Features” was not selected, nor were any of the features, the role has not be installed.

Following that, I installed the Windows Features and Role I needed using:

Install-WindowsFeature -ComputerName VM NET-Framework-Feature, NET-Framework-Core

This failed. If you notice from the below error, the installer cannot find the right files locally on the machine.
PS Error
So, in order to fix this, we have to insert the installation DVD (mount the ISO if virtual) and specify the path.

Install-WindowsFeature -ComputerName VM NET-Framework-Feature, NET-Framework-Core -Source D:\sources\sxs

This will allow the .Net Framework 3.5 to be installed. If you run:

Get-WindowsFeature -ComputerName VM *NET*

This will verify the needed .Net Framework 3.5 actually installed.

PS Successful

***UPDATE – you CAN install .Net Framework 3.5 on server core.

Edit NIC on vSphere using PowerCli

If you need to edit the VM’s NIC after you deploy the VM using vCenter, it’s grayed out. I wanted to change it from E100E to VMXNET3.

E100E

 

In order to make this change, you need to utilize PowerCli. Make sure you connect to vCenter using:
Connect-VIServer VCSA

After being connected, run:
Get-VM VM | Get-NetworkAdapter

To set the NIC to VMXNET3 run:
Get-VM Server | Get-NetworkAdapter | Set-NetworkAdapter -Type VMXNET3
Then confirm the selection by entering ‘Y’

Done

 

Once that is done, run the following command again:
Get-VM VM | Get-NetworkAdapter
As you can see, the Type is now Vmxnet3.

VMXNET3

 

Now, if you check the GUI, you’ll notice it has changed.

Final GUI

Edit Shared Mailbox SMTP Address with Powershell

Connect yourself to Exchange 2013. In this demo, I’m using office 365.

$LiveCred = Get-Credential
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
Import-PSSession $Session

Once connected to Exchange 2013 and all of the modules have been imported, run:

Get-Mailbox -Identity xxx@domain.com

This will display tons of information about the shared mailbox. To shorten the information down to what I wanted, I ran:

Get-Mailbox -Identity xxx@domain.com | Format-List EmailAddresses

Make sure you utilize “EmailAddresses” property, not EmailAddress.

This will show you the SMTP information, and the line will look similar to:

EmailAddresses: {SMTP:xxx@domain.com, smtp: xxx@domain.onmicrosoft.com}

Now that you know what the SMTP (since it’s capital, it’s the primary address) you need to change it. Run the following command:

Set-Mailbox -Identity xxx@domain.com -EmailAddresses xxxNew@domain.com

Pretty simple. When you run the “Get-Mailbox” command again, you will see this:

EmailAddresses: {SMTP:xxxNew@domain.com, smtp: xxx@domain.onmicrosoft.com}

Now, if you send email the xxx@domain.com, it will bounce back, if you send it to xxxNew@domain.com the mail will be received in the shared mailbox.

** If you’re trying to change an email address that is part of your synchronized Active Directory, this will fail. You MUST change the SMTP setting through your Active Directory.