Windows 10: The user signed into my domain on my computer is corrupted, I need available hot keys to...

My user account was corrupted from deleting registry keys and when I tried to sign into the “other” account it’s stuck on the corrupted profile with no system how can I return to admin without shutting it down? Shutting it down will probably cause it not to load at all. I just want to switch back into admin but there’s no screen to do that.when I do attempt to go into safe mode or recovery it takes me straight to the bios and beeps and will not allow me to recover, it’s been doing this for a long time. An obvious tactic by someone to keep me from recovering my account and computer,

:)

 

When playing games the hot keys are active

Hi Chris,

Thank you for your interest in Windows 10.

I suggest you to follow the steps below to disable Hot Keys and check if that helps.

• 
  Right click anywhere on your desktop screen and select Graphics Options.
  
• 
  Navigate to Hot Keys and then click on Disable.
  
• 
  Check if issue persists.
  

Hope this information is helpful. Please do let us know if you need further assistance, we’ll 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

 

Can't login as local user after adding a computer to a domain


Here are the steps I took. Please tell me if I should have done differently.

1. On the server end add the user and computer to the domain in advance.

2. Fresh install windows 10 and make the first username Admin.

3. Once at desktop rename PC to match PC name on domain i.e. Workstation001.

4. Add computer to mydomain.local and when asked for username and password I entered the credentials for the new user.

5. Restarted the PC and signed into mydomain\newuser without any problems.

However now when I try to access the original local Admin account by typing 'Workstation001\local Admin' as the username and then the password. It keeps saying password invalid.

So I logged back into the domain account and tried resetting the password to Admin and then tried signing in as admin again, still no luck.

Currently there are 2 accounts on the computer one of them is a local/domain account for newuser and the other is a local Admin account which I cannot access.

What kind of glitch is this? Should I have not joined the domain through the original Admin account and instead added a local user to the PC 'newuser' and then sign in as that user locally then add them to the domain through their own local account? I didn't think this was necessary.