Technical

Activating RMS in Office 365

Microsoft Azure Rights Management provides a comprehensive policy-based enterprise solution to help protect your valuable information, no matter whom you share it with.

These policies help improve data security using both Both Information Rights Management and Office 365 Message Encryption

To activate rights management:

  1. Log into Office 365 with an account which has been assigned an administrator role. To do this simply go to the portal site: https://portal.office.com
  2. Click on admin to enter the Office 365 admin center via the admin app icon

  3. In the left pane, expand the service settings
  4. Click on Rights Management to enter the Rights Management dashboard
  5. Here on the dashboard, click on Manage
  6. Click on Activate to active Rights Management

For additional options and steps please have a log over on technet

 

Thanks for visiting – jermal

Remove Wireless Profiles in Windows 10

Similar to my previous post ‘Windows 8: Remove Old Wireless Network Profiles‘ the following are steps which can be preformed in both the command prompt or PowerShell prompt.

Task: Clean up all wireless profiles in Windows 10

Requirements:

  • PowerShell or Command Prompt
  • Elevated Privileges

Steps:

  1. Open, a PowerShell prompt or Command prompt as Administrator
  2. Enter netsh wlan show profiles to show all wireless profiles

  3. Enter netsh wlan delete profile name=”ProfileName” to delete a particular profile by name

     
  4. Or enter  netsh wlan delete profile name=”*” to remove all saved profiles

For more info on managing wireless networks on Windows 8, 8.1, 10 check out the following: Manage wireless network profiles

 

I hope you enjoyed this short post, thanks for visiting – jermal

 

Tech Short: Using PowerShell to join Computer to AD Domain

Working on a server installation I decided to use a simple yet effective power-shell command to join a Windows Server 2012/R2 system to our domain.

For the sake of brevity lets just show you.

Requirements:

  • Admin access to the computer/server you are joining to the domain along with permissions in the AD domain to join machines
  • Connected to the network where the domain is accessible
  • Obtain an network ip address along with dns that can resolve the domain you are joining
  • PowerShell

Steps:

  1. Launch PowerShell as an Administrator
  2. Issue the following command example: Add-Computer -DomainName <domain name> -Restart

You will be prompt for a username and password at this point. Enter in the correct credentials and soon after a restart will occur.

When you resume from the restart you can now log in on this workstation/server with domain credentials.

Additional info can be found on Technet

I hope you enjoyed this short, thanks for visiting – jermal

VMware: vCenter Server Appliance 6.0 Update 1

That time has come, when you upgrade vCenter 6.0.  Here are some quick simple steps to see this done.

As always, its a good idea to have a backup before proceeding.  In my case I used a snapshot of my appliance. This was done by me connecting directly to the ESXi and creating a snapshot.

And here are the steps to start this process:

  1. Download the VCSA 6.0 Update 1 from  the VMware Patch Download Website. File-name: VMware-vCenter-Server-Appliance-6.0.0.10000-3018521-patch-FP.iso
  2. Mount the VCSA 6.0 Update 1 Patch ISO to your VCSA 6.x appliance. I attached the ISO by logging into the ESXi and then attaching to the guest appliance
  3. Next is to be logged into the VCSA 6.x appliance via SSH – note this must be an admin account.  I used the local root user and password
  4. Run the following command to begin the installation process: software-packages install –iso –acceptEulas

  5. When completed issue the reboot command: shutdown reboot -r “Updated, thanks to my buddy jermsmit”

     

Congrats you have upgraded.

Info sources:

VMware KB – for additional info

William Lam – who’s tweet informed me of this release, thanks dude

 

I hope you enjoyed this post, thanks for visiting – jermal

Creation of Virtual Machine Fails – StatusCode: 610–MandatorySysPrepEntryNotFound

Working with the team in creating new virtual machine templates I found that some of our Windows 7 templates when they are being deployed with the following error:

Virtual Machine Manager was unable to find a value for the required Sysprep parameter ProductKey. (StatusCode: 610–MandatorySysPrepEntryNotFound)

I attempted to do some google searching which gave me no information for this issue and I started thinking about the issue in detail. Perhaps the sysprep operation requires a key. Then again its right there in the error message which I overlooked at first glance

So I did just that.

I logged into my MSDN and obtained a MAC key, applying it to the template, saved my change and attempted the process again. This time my deployment worked.

I decided to use a KMS Client setup key for these images as our network supports KMS activation.

For a list of KMS Client Keys: https://technet.microsoft.com/en-us/library/JJ612867.aspx

 

Another error encountered was:

Virtual Machine Manager was unable to find a value for the required Sysprep parameter LocalAdminCredential. (StatusCode: 610–MandatorySysPrepEntryNotFound)

As we did above we needed to define a local admin account (user/password) to be added to our deployments.

 

I hope you enjoyed this post, thanks for visiting – jermal

Tech Short: How to uninstall Windows 10

Of of my visitors wrote me asking how to uninstall Windows 10. I provided the steps in my response so I am sharing them here.

Please *note* that these steps only apply to those upgrade installations of Windows 10.

  • Open up Settings via the Start menu
  • Click Update & Security and then Recovery
  • Under the Go back to Windows 7 or Go back to Windows 8, click Get started

Follow the steps through the rest of the process to get back to your previous version of Windows.

If you used this post to assist you please leave me a comment on why you uninstalled, I would like to hear about it.

 

 I hope you enjoyed this techshort, thanks for visiting – jermal

System Center – Virtual Machine Manager Error (12700)

Creating several templates in SCVMM today I encountered the an error with the id of ‘12700’ with the message:

Error (12700)
VMM cannot complete the host operation on the s0106hvlab5.jermsmit.local server because of the error: ‘W10_64_jermsmit’ could not initialize. (Virtual machine ID B4B770E3-9DD7-4C3F-B2A5-36CA37151600)

Not enough memory in the system to start the virtual machine W10_64_jermsmit with ram size 4096 megabytes. (Virtual machine ID B4B770E3-9DD7-4C3F-B2A5-36CA37151600)
Unknown error (0x800a)

Recommended Action
Resolve the host issue and then try the operation again.

In my situation I tracked the issue down to the following:

Cause: I was overdoing it by running many conversions without the memory resources being available

Solution: Throttle my activity

Tech Short: How to use System Center – App Controller 2012/R2

Instruction on using System Center – App Controller 2012/R2 – Lab Server Environment

The following is a simple set of instruction to get some of my lab users up and running quickly in System Center App Controller used as a self service portal for a lab environment

Minimum Requirements to Use
• IE 8, 9 or later
• Silverlight 4.0 or later

Location
URL Address: https://something.tld.com

Signing In
To sign-in, use your network login where the username is passed in either of the following two formats:
• username@domain
• domain\username

Creating a New Virtual Machine Instance

  1. Select Library on the left
  2. Select Templates
  3. Select the Template you want and click “Deploy” (Button or context menu)
  4. Configure the Cloud
    Click the “Configure…” link to configure the Cloud
    Click OK on the dialog as there is only one Cloud.
  5. Configure Virtual Machine
    Click the “Configure…” link to configure the Virtual Machine
    Set Virtual Machine Name to a name that includes your Name and Last initial if needed. Spaces are accepted.
    Set Description
    Click OK
  6. Click “Deploy” Button on bottom right of screen (this may take a few minutes)
    The Yellow bar on the bottom will provide a status to when the virtual machine deployment has started and when it has finished.
    The status can also be viewed under Jobs. Once the Job is Completed you will see the virtual machine when you view Virtual Machines.

Using Virtual Machines

Starting a VM

  1. Select Virtual Machines
  2. Select the Virtual Machine you wish to run
  3. Click “Start” (button or context menu)
  4. Click “Console” (button or context menu)
  5. If this is the first VM you are running, you will need to install a plug in

 

 

 I hope you enjoyed this techshort, thanks for visiting – jermal

Tech Short: PowerShell: Networking Diagnostics

Listen ‘tracert’ its not you, its me…  I am not ending my long term relationship with the diagnostic tools which I have used for many years now.  I am just exploring others, and in doing so going on a “break”.

I recently starting using PowerShell more often and wondered is there a tool which can do what ‘tracert‘ does and maybe more.

This is where the PowerShell command  Test-NetConnection comes into the picture.

It does many of the functions of tracert which an out-put which at this point I favor far more.

Here are some examples:

Here is an example of using Test-NetConnection to test connectivity to jermsmit.com

ComputerName : jermsmit.com
RemoteAddress : 184.168.16.1
InterfaceAlias : Wi-Fi
SourceAddress : 1.2.3.150
PingSucceeded : True
PingReplyDetails (RTT) : 80 ms

 

Same test as above using the –TraceRoute flag return the list of hosts on the path to the specified target jermsmit.com

ComputerName : jermsmit.com
RemoteAddress : 184.168.16.1
InterfaceAlias : Wi-Fi
SourceAddress : 1.2.3.150
PingSucceeded : True
PingReplyDetails (RTT) : 82 ms
TraceRoute :
1..2.3.150
96.120.75.45
68.86.221.197
68.86.209.165
68.86.90.21
68.86.85.53
68.86.85.25
68.86.83.82
173.167.58.134
184.168.0.69
184.168.0.69
97.74.255.129
184.168.16.1

As you can see form the examples its a very useful tool in PowerShell, also giving you information about which network interface you are testing from.

What I have also found out is there is an alias for  Test-NetConnection. To use this all you need to do is simply type ‘tnr‘ following by the command syntax.

For more info on using Test-NetConnection type: Help Test-NetConnection in the PowerShell command prompt – Results may looking similar to what I have shown below:

 

 

 

 I hope you enjoyed this techshort, thanks for visiting – jermal

 

Tech Short: Change Password VMware vCenter 6

The day would come where I would need to change my password in vCenter… Today was that day; Thankfully vCenter places am informative notice of your expiring password.

Here is how you can change your password using vCenter 6:

Log into vCenter 6

  1. Click Home.
  2. Click Administration.
  3. Click Single Sign-On > Users and Groups.
  4. Click the Users tab.
  5. Right-click the affected user account, selecting edit user
  6. Enter in the current password, followed by your new (it could be the same, I don’t ever recommend this practice)
  7. Click OK to save changes.

 

I hope you enjoyed this techshort, thanks for visiting – jermal