Need to Join Windows XP Clients to a 2016 Domain
-
@EddieJennings said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@dbeato said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
We have a new 2016 functional level domain. We have two Windows XP clients that need to join it. They are getting this error: ""
We are guessing that it is a functional level mismatch. Anyone know what is needed to do a join?
So what is the error?
LOL, I tried to grab it and couldn't. Something about the DC no longer being available.
Saw that with Server 2003. Issue (despite earlier thread posts) was caused by us turning off SMBv1
Yeah - I've definitely seen SMBv1 disabled cause issues for older OS's, though can't be certain it was for authentication against AD.
-
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@gjacobse said in Need to Join Windows XP Clients to a 2016 Domain:
I have been waiting for someone to ask the obvious...
WHY are you still using Windows XP??? Like... wow that is old.
But really - if it's what they have - it's what has to be used.
Are there any other computer OS Versions (Win 7, Win 10) - do they join okay?
$100K update fee.
That update fee should be seen as a cost of business to ensure the business isn't being put at risk.
-
@DustinB3403 said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@gjacobse said in Need to Join Windows XP Clients to a 2016 Domain:
I have been waiting for someone to ask the obvious...
WHY are you still using Windows XP??? Like... wow that is old.
But really - if it's what they have - it's what has to be used.
Are there any other computer OS Versions (Win 7, Win 10) - do they join okay?
$100K update fee.
That update fee should be seen as a cost of business to ensure the business isn't being put at risk.
LOL - as if
-
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
@DustinB3403 said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@gjacobse said in Need to Join Windows XP Clients to a 2016 Domain:
I have been waiting for someone to ask the obvious...
WHY are you still using Windows XP??? Like... wow that is old.
But really - if it's what they have - it's what has to be used.
Are there any other computer OS Versions (Win 7, Win 10) - do they join okay?
$100K update fee.
That update fee should be seen as a cost of business to ensure the business isn't being put at risk.
LOL - as if
I know. . . I do. I used to work for a sheet metal engineering company and if the computer operated there wasn't a chance in hell of upgrading it.
We did get a new laser at one point and boy was that thing nice compared to the 35 year old system that was still being used. . .
The only reason that it was purchased was the existing laser couldn't meet the tolerances required. Functional, but for items having lower tolerances.
-
I'm sure you'd like to stay within MS for this, but a year or so ago, I had a similar issue at a machine shop. After a few hours of getting no where, we threw an old copy of Lantastic on the CNC PC and the server. They were up and running in about 15 minutes.
Maybe this will get you thinking from another angle that may lead you to your solution.
-
Does the XP machine need to be part of the domain? What about working around that issue?
-
@Dashrender considering the title I would say, yes XP needs to be attached to the domain.
-
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
Does the XP machine need to be part of the domain? What about working around that issue?
We removed the domain completely.
-
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
Does the XP machine need to be part of the domain? What about working around that issue?
We removed the domain completely.
So now you're what - trying to use a 2019 SMB file share or something?
-
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
Does the XP machine need to be part of the domain? What about working around that issue?
We removed the domain completely.
So now you're what - trying to use a 2019 SMB file share or something?
What does file share have to do with AD? Completely disconnected concepts.
-
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
Does the XP machine need to be part of the domain? What about working around that issue?
We removed the domain completely.
So now you're what - trying to use a 2019 SMB file share or something?
What does file share have to do with AD? Completely disconnected concepts.
True - I was making my own leap -
So - where does this stand now then??
-
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
@scottalanmiller said in Need to Join Windows XP Clients to a 2016 Domain:
@Dashrender said in Need to Join Windows XP Clients to a 2016 Domain:
Does the XP machine need to be part of the domain? What about working around that issue?
We removed the domain completely.
So now you're what - trying to use a 2019 SMB file share or something?
What does file share have to do with AD? Completely disconnected concepts.
True - I was making my own leap -
So - where does this stand now then??
We removed AD. It turned out that it had been installed without evaluation and was serving no real purpose, but was posing a significant risk.
