Can a domain server be shut down? Why can t the server be shut down?

No, it cannot be turned off. Shut down. Other machines cannot be connected. It can be shut down when no one is using it, so that no machine is connected to the domain server.

After the domain server is shut down. The client can log in as normal. But it's no different from a normal stand-alone machine. Some features are only available if the domain server is open.

Hello: According to your description, xp sever?? I haven't heard of it, but the domain server is not completely unavailable, for example, the computer with the domain login once with the domain number, the next login, if the number is the same is not needed, if it is the first time, it must be wanted

Hope it really helps you, not fooling.

If the domain name knowledge xpserver is a unilateral domain, it is recommended not to make this comparison, it is recommended to have a chip.

Once the domain is set up, it can not only manage computer accounts and policies, but also unify through the LADP directory service, including file sharing, production systems, etc., and the above, through the group test rate, you can set the asynchronous cache when logging in to the client computer (at present, the default asynchronous cache above 2008), so that closing the domain server does not affect the login of the client computer, but the entire function realized through the domain environment cannot be used.

Asynchronous caching can be found in Group Test Rate - Computer Configuration - Security Settings - Local - Security - Interactive Access.

To build a domain service, it is recommended to learn more about group policy and general services such as DNS, NTP, and DHCP.

1 This is related to the Group Policy setting, if the Group Policy is set not to allow the client to cache the previous login, then the client will definitely not be able to log in to the domain after the domain control is shut down.

2 If you don't have the settings, you can log in three times.

3 The default method is that the client caches the previous login, that is, the client can log in three times under the default setting.

4 Setup Method:

The number of previous logins that can be cached.

Start - Administrative Tools - Active Directory Users and Computers, right-click on Domains - Properties - Group Policy, select Default Domain Policy - Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options - Number of Previous Logins that Can Be Cached, set to 0.

If you want to use your own computer as a server, you must keep it on 24 hours a day, and you can't turn it off.

I guess you can't turn it off, if you only have this one domain controller.

In this case, as long as you log in to the computer locally with administrator, exit the domain and rejoin the domain, there are still problems to discuss together.

On the member server that you need to be shut down by a domain member, turn on Local Group Policy and grant.

domain users group to turn off the system's permissions, and there should be no problem.

The system server has a column**limit,When you want to shut down** run immediately,Whether you log out or restart (unless you force a shutdown) will not shut down,This is also a kind of data protection for the server,Once the shutdown data will be lost in some aspects (and your computer's time can not be changed),) The change time shall not exceed 30 minutes (of course, depending on the limit of your own server) If you change it, the program will report an error prompt you,Let you change the time in the restart! Of course, you're a server after all, so it's best not to restart it, and if you want to restart, just retire the server first! If you don't shut down the server and the shutdown is not successful, the server icon in the toolbar may not be displayed, then you can turn off the options in the process through the task manager (ctrl+alt+delete), if you don't know which process it is, you can put the process name in it, you can contact me if you don't know! Hehe.

The server is responsible for the data exchange and backup work within the entire LAN or WAN, and generally uses dual hard disk backup. For example, Tencent's QQ server, the reason why you can enjoy 24 hours of uninterrupted online is the credit of the server. As for the ** server, it takes on the responsibilities of more web hosting, and the question you open is also one, how can it be shut down?

After the shutdown, these netizens can only scold the street, so this is a professional problem. Some of them are for scientific budgeting, some are for military missions, some are for civilian entertainment, and the nature of the decision is the reason why it cannot be shut down.

1.When you first join the domain, you add a username to your computer, just like you would if you were creating a new user in workgroup mode. If you turn off computer A while you are adding a domain to computer B, you can't join it.

The impact of the domain server being shut down is at most that the sharing is not available...

I had to have a Change Password item (I don't know if you said this)3I don't understand what you mean.

2.In your AD controller, add a password to each person, or press Ctrl+Alt+Del on the client to set a password for the client?! If you don't want users to log in to the machine, you can switch to the local state and set a password (not to them), and they can only log in with the domain user.

After the domain is shut down, the client has only 10 caches to log in, beyond which it will not be able to log in.

When the computer is shut down, B can only log in to the local machine, but cannot log in to the domain.

2.Use the administrator to log in to the domain on A or B, and change the password in the same way, you can press Ctrl+Alt+Del and choose to change the password.

3.The password saved in the local secure account database is used to log in to the client administrator, and the password is used to log in to the active directory.

Don't shut down too often, it's okay once in a while.

After the restart, it is similar to the original, except that no one else can access it when it is restarted.

If the service is local, the problem will come back immediately, and if the user happens to cache locally, it can last for half an hour, anyway, if you turn it off, there will be a problem with the local immediately.