Windows 10: Remote connection struggles Definitions and domains and servers

These two terms make sense to me. When they use terms like server or client or host Remote Access
Remote Support I am unsure what they mean.
However these terms make it clear:

Operator/Admin side: This is the guy who is moving the mouse
Remote partner/client side: This is the Unattended side.

I live in a small town we have very few servers here. Many peer to peer networks with 3 and 5 computers
When I read about Remote Desktop connection they assume that a server is present.
So the if the Remote partner/client side is on peer to peer network and has windows 10 home I may be able to use this program called. bitvise SSH server .
During the install of Bitvice SSH server it get these optoins.:



I think a non DC computer is one that is on a peer to peer network that does not have any type of server that controls all the permissions. A non DC server is a computer that is peer to peer with no server?
Apparently I will need to use the Standard Edition to make remote desktop work on a computer that has no server only has internet access and I think that I can use this program in standard Edition to connect to a windows 10 home system. Even if it does not have a domain server. AM I correct on this??

When the Remote partner/client is win 10 home and is only a peer to peer and has no windows server will this Bitvise SSH server work - Like can it be setup so no person needs to be on the other end ?
Currently if I could get chrome remote desktop to work unattended that would be perfect but it wont. Every 4 minutes someone on the other end must press continue or the whole connection process needs to be restarted. What I read is ssh is needed.

If I buy bitvice can I use it on as many computers as I want as long as I am using the same computer for Operator/Admin side? If not are there other solutions ?

Thank you

:)

 

Remote connection struggles Definitions and domains and servers

These two terms make sense to me. When they use terms like server or client or host Remote Access
Remote Support I am unsure what they mean.
However these terms make it clear:

Operator/Admin side: This is the guy who is moving the mouse
Remote partner/client side: This is the Unattended side.

I live in a small town we have very few servers here. Many peer to peer networks with 3 and 5 computers
When I read about Remote Desktop connection they assume that a server is present.
So the if the Remote partner/client side is on peer to peer network and has windows 10 home I may be able to use this program called. bitvise SSH server .
During the install of Bitvice SSH server it get these optoins.:



I think a non DC computer is one that is on a peer to peer network that does not have any type of server that controls all the permissions. A non DC server is a computer that is peer to peer with no server?
Apparently I will need to use the Standard Edition to make remote desktop work on a computer that has no server only has internet access and I think that I can use this program in standard Edition to connect to a windows 10 home system. Even if it does not have a domain server. AM I correct on this??

When the Remote partner/client is win 10 home and is only a peer to peer and has no windows server will this Bitvise SSH server work - Like can it be setup so no person needs to be on the other end ?
Currently if I could get chrome remote desktop to work unattended that would be perfect but it wont. Every 4 minutes someone on the other end must press continue or the whole connection process needs to be restarted. What I read is ssh is needed.

If I buy bitvice can I use it on as many computers as I want as long as I am using the same computer for Operator/Admin side? If not are there other solutions ?

Thank you

 

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.

 

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