Windows 10: Remote laptop domain login

I have laptops Hybrid joined to an Azure/AD domain. I want remote users to have the ability to login that have never logged into their laptop before. The laptops are joined to our AD domain.I am told users could do this in the past by logging in with the full e-mail address ex. *** Email address is removed for privacy *** but this has stopped working. The user has been walked through connecting to their home network, but they get the domain is not available message.1. Is this even possible for Hybrid joined devices?2. What settings are needed to enable this functionality in 365 and/or on the laptop?Thanks

:)

 

Remote Desktop Login Failed

I just purchased a new Windows 11 system and I am using another Windows 11 system on my laptop to access the system through remote desktop and I get an error that says that the login failed. Something in the new Windows 11 system is blocking logins from remote desktop:

• I am using my standard Windows credentials to login locally. I have Administrator rights to the system, and a local login works fine.
  
• I can use Remote Desktop to login to another similar Windows 11 desktop using remote desktop with the same credentials and that also works fine.
  
• I've enabled Remote Desktop access in settings and specified my account as being authorized to login with Remote Deskttop.
  

I've gone through all the support articles I could find on the internet on this problem and I implemented the group policy fixes that have been recommended but it still hasn't resolved the problem. Any help or suggestions would be appreciated.

Thanks,

 

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

 

How to remove "HP Connected Remote" as a sign in account ?

Hi Dave,

Thank you for writing your query in Microsoft Community.

• 
  Is your computer connected to a domain network?
  

HP Connected Remote is an app that comes preinstalled on select Windows HP computers. I would suggest you to follow the below steps and check if it resolves this issue.

• On the Windows 10 Start screen, type hp connected remote.
• Click HP Connected Remote from the Apps search results.
• Click Settings, and make sure Enable HP Connected Remote is turned On.

Reply us back with the status of this issue. We will be glad to assist you.