Windows 10: Using Teams in HyperV with Company domain

I have a company laptop with Teams and obviously that works fine. However, I wanted to install Teams on my personal pc and decided to use a HyperV vm to run as it needs to use a company domain and that takes over control of certain aspects.

In particular, it requires you to use a PIN of at least 6 digits.

This is where I ran into a big issue with HyperV.

I made a previous post about using HyperV with a PIN i.e. it will not use enhanced mode.

I thought this was a bug but it turns out this is BY DESIGN.

If you have a PIN, you can only use HyperV in BASIC mode which is no use for Teams as you do not get any audio!

I really thought I was screwed i.e.to use Teams for company account, I would have to join domain and install it on host accepting restrictions which I really did not want to do.

As it happens, my Company also accepts two factor account authentication for Teams but when you install and set it up, it asks you to join the domain and set pin, and then bitlocker whole drive.

However, it also gives option NOT to join a domain and only sign into Teams. I tried this and it installs and it runs ok without need for PIN or bitlocker. I cannot access my company onedrive account directly as I have not joined a domain.

However, I can still access company onedrive via MS Office 365 so no big deal just slightly less convenient. Strangely, 2FA is allowed Company for this with no need for PIN or bitlocker.

So I now have a nice VM dedicated to work use without "polluting" my main PC.

However, not being able to use HyperV and a PIN in enhanced mode is a PITA as I have to type in full password each time I run VM (and less secure in theory).

:)

 

Using Teams in HyperV with Company domain

I have a company laptop with Teams and obviously that works fine. However, I wanted to install Teams on my personal pc and decided to use a HyperV vm to run as it needs to use a company domain and that takes over control of certain aspects.

In particular, it requires you to use a PIN of at least 6 digits.

This is where I ran into a big issue with HyperV.

I made a previous post about using HyperV with a PIN i.e. it will not use enhanced mode.

I thought this was a bug but it turns out this is BY DESIGN.

If you have a PIN, you can only use HyperV in BASIC mode which is no use for Teams as you do not get any audio!

I really thought I was screwed i.e.to use Teams for company account, I would have to join domain and install it on host accepting restrictions which I really did not want to do.

As it happens, my Company also accepts two factor account authentication for Teams but when you install and set it up, it asks you to join the domain and set pin, and then bitlocker whole drive.

However, it also gives option NOT to join a domain and only sign into Teams. I tried this and it installs and it runs ok without need for PIN or bitlocker. I cannot access my company onedrive account directly as I have not joined a domain.

However, I can still access company onedrive via MS Office 365 so no big deal just slightly less convenient. Strangely, 2FA is allowed Company for this with no need for PIN or bitlocker.

So I now have a nice VM dedicated to work use without "polluting" my main PC.

However, not being able to use HyperV and a PIN in enhanced mode is a PITA as I have to type in full password each time I run VM (and less secure in theory).

 

Purchasing a web domain

I would suggest using this company. Used them several times for expiring domains and have snagged every single one of them.

Domain Name Auction Marketplace - Buy and Sell Domain Names - SnapNames.com

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW