Difference between revisions of "Domain Server"
(→How to join Windows 8/Windows 2012 to an IPBRICK v6.x domain) |
(→How to join Windows 8/Windows 2012 to an IPBRICK v6.x domain) |
||
| Line 70: | Line 70: | ||
[[File:1.png]] | [[File:1.png]] | ||
| + | |||
[[File:2.png]] | [[File:2.png]] | ||
| + | |||
[[File:3.png]] | [[File:3.png]] | ||
| + | |||
[[File:4.png]] | [[File:4.png]] | ||
| + | |||
[[File:5.png]] | [[File:5.png]] | ||
| + | |||
[[File:6.png]] | [[File:6.png]] | ||
| + | |||
[[File:7.png]] | [[File:7.png]] | ||
| + | |||
[[File:8.png]] | [[File:8.png]] | ||
| + | |||
[[File:9.png]] | [[File:9.png]] | ||
| + | |||
[[File:10.png]] | [[File:10.png]] | ||
| + | |||
[[File:11.png]] | [[File:11.png]] | ||
| + | |||
[[File:12.png]] | [[File:12.png]] | ||
Revision as of 13:55, 27 October 2015
Contents
F.A.Q.
Is it possible to run a script when the user logs in the domain, at a windows workstation?
Yes. it is possible to run a script when the user logs in the domain at a windows workstation. These scripts are called netlogon scripts, and are to be published at the domain controller shared folder called netlogon.
In an IPBRICK setup all users are, by default, setup to look for netlogon script called [user's login].bat (ex.: for a user with the login johndoe the file should be named johndoe.bat).
The netlogon shared folder is located at //[server's name]/netlogon/ (ex.: //ipbrick/netlogon). On the server's file system you may find this folder located at /home1/_netlogon.
NOTE:
- share/file permissions: users members of "Domain Admins" group have read-write permissions, all other users have read-only permissions in the netlogon shared folder. So, only "Domain Admins" user's are authorized to create/edit/delete netlogon files (scripts).
- file/script creation: by default the logon script files do not exist, they are not created automatically. Domain users are automatically (by default) defined to look for [user's login].bat, meanwhile this file is not automatically instantiated, so when you access for the first time to netlogon share you will find it empty.
Is it possible to join Windows 10 to an IPBRICK v6.x domain?
***CONSTRUCTION IN PROGRESS***
Yes, it is. But before you start the process of joining a machine in a domain, you have to know the username/password of the administrator of the windows machine. Then, you can start the migration process.
Therefore you have to:
- Press [windows];
- Select My Local Network;
- Select Network Connections;
- Right click on the icon Local Network Connection and select Properties;
- Choose TCP/IP in the open window and click on Properties;
- Choose Get the IP Address Automatically in the open window and then select Get the DNS server addresses automatically;
- Close the network properties window.
The next step is to confirm that the machine IP address is the same that was introduced in IPBrick.I.
Therefore you have to:
- Press the keys [windows]+[R];
- cmd [ENTER];
- ipconfig /all;
- Check the information in the IP Address field.
If the IP address is not the one introduced in IPBRICK you have to release it and renew it with the following commands:
- Press [windows]+[R] keys simultaneously;
- cmd [ENTER];
- ipconfig /release;
- ipconfig /renew;
- ipconfig /all.
If the machine IP address is right you can join the machine in the domain:
- Press the keys [windows]+[pause] and open the System Properties;
- Select ”Computer Name”, click on ”Change...” and give the computer a name (the name must have been created in IPBrick.I before);
- Press button ”more..” and add the dns machine domain. Do not select the option Change the primary DNS suffix when the association to the domain is changed.
How to join Windows 8/Windows 2012 to an IPBRICK v6.x domain
***CONSTRUCTION IN PROGRESS***
To join Windows 8/Windows 2012 perform the following procedure:
- Create the register on IPBrick in Machines Management;
- Apply changes on the registry according to the attached zip (double click on the reg and intersperse on the registry), and reboot the station/server;
- These machines have no specific/functional terminal to join themselves to a windows domain on an IPBrick level, so it is used a profile "migration tool" (Note: At this time, the windows station/server is configured in workgroup "workgroup".);
- http://www.forensit.com/downloads.html
- Create a temporary user in IPBrick - migra2012 - and apply configurations;
- Create a local user in the Windows station/server with the same login (migra2012), log in locally with this login and then log out;
- Log in with the local administrator of the station, confirm network configurations (use DNS and WINS pointing to the IPBrick server);
- Execute the application "profwiz.exe" to migrate the profile "migra2012" and, simultaneous, perform "join to the domain" of IPBrick (indicate windows domain served through IPBrick);
- The station/server reboots, and it becomes possible to log in with any login of the domain, and the profile "migra 2012" can be removed.
