Jump to content
RESET Forums (homeservershow.com)

Install Connector Software without joining Domain?


kamaran
 Share

Recommended Posts

I know there was a previous registry fix for this for R1, however it doesn't seem to work for me (I've tried using 2 machines) with R2.  The clients succesfully install, but they DO join the domain and it creates new Windows profiles on each PC.

 

Can anyone advise if they have joined clients succesfully without joining the domain and if so, provide a step by step guide?

 

 

Link to comment
Share on other sites

  • Replies 26
  • Created
  • Last Reply

Top Posters In This Topic

  • Drashna Jaelre

    4

  • jmwills

    6

  • ikon

    5

  • kamaran

    5

To skip joining the domain during a client deployment.

On your client computer, go to Start and search for command prompt "cmd".
In the search results, find cmd.exe and run as administrator.

Type the following command prompt:
reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1

Complete the steps on the Connect Computers to the Server Help topic.

Link to comment
Share on other sites

Were the clients previously joined?  If os, you will have to remove them form AD and rejoin them back to a Workgroup before proceeding again.

Link to comment
Share on other sites

Were the clients previously joined?  If os, you will have to remove them form AD and rejoin them back to a Workgroup before proceeding again.

They were only in a workgroup before, but are now in the DOMAIN

 

So from this point, what steps do I need to take please?

Link to comment
Share on other sites

This didn't work for me when the client was a member of a existing domain and I attempted to join R2 off domAin for client backup only. It works on R1.

Link to comment
Share on other sites

I have found a horrible workaround

 

Install client as normal on PC

 

System Restore PC back to before the client installation

 

Don't make any modifications on the server side

 

Install client again on PC - this time it will give you error messages that the PC already exists - choose OK/Yes and won't add it to the domain again.

Edited by kamaran
Link to comment
Share on other sites

First of all, the client MUST be in a workgroup before attempting to install the connector software.  Make sure the client computer object does not exist in the R2 domain (whatever that name is). 
 

Then run the registry hack and then install the connector software.

 

 

Why not just let the server does what it's supposed to do?

Link to comment
Share on other sites

That's one benefit of the WSE12 R1 connector. You can still skip the server domain and Allow the client to remain connected to a corporate domain. Yet it sill still backup.

Edited by Jason
Link to comment
Share on other sites

I have successfully used the registry fix with Windows Server 2012 Std R2 with the Essentials Role.

 

I have migrated 6 machines from a WHS2011 environment using a single workgroup to the new 2012 R2 server. They are a mix of Win 7 Home, Win 7 Pro, Win 8 Pro and Win 8.1 Pro.

 

Client Backups are all working fine and so far I have tested bare metal restores over the network to a Win 7 Pro and a Win 8 Pro client.

 

I did not have to do anything like what Kamaran reported.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×
×
  • Create New...