Windows 10: Stuck at "Welcome" after logging into company domain?

Recently started having an influx of issues with newly imaged Win10 1903 setups, these are joined to a corporate domain and some of my users will get stuck at "Welcome" after entering their password to login.

I've tried a number of things, but no profiles are able to log in (even the local admin account), only if I go to safe mode. I've tried disabling all but MS services, sfc scan doesn't find anything, I've moved to the suspected PC onto a group with no GPO/group policies, but I'm suspecting it is something on the computer itself, but it won't communicate with the domain regardless (won't re-join once taken off).

not sure if anyone else has run into this issue but I'm open to explore options.

submitted by /u/ydgit889
[link] [comments]

:)

 

I can't log in and domain problems

Hi Tucker,

There are several factors which might have affected the log in issue, namely: a restriction set by the network domain administrator, if your computer is connected to a network domain; or a recent update or program installed prior to the issue. To help you
resolve the log-in issue, kindly answer the following questions:

• Were there any changes made prior to the issue, or before the PC was reset?
• Are you using a PC connected to a network domain?
• What are the troubleshooting steps that you have done in an attempt to resolve the issue?
  

We look forward to your prompt response.

 

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