End your computer session. Ending your session with Windows xp Professional. Logging off from Windows xp Home Edition
In the Microsoft Windows operating system, each user can set their own parameters necessary for their work. Each user has their own account. You can change a user or end a user session in one of several ways.
Instructions
You will need
- Explore the Log Off mode in the Windows operating system.
Instructions
The need to forcefully shut down a user mainly arises in the following cases:
- Updating the information base;
- Adding a new metadata object to the configuration;
- Carrying out preventive and repair work on the server;
- A hung user session is preventing the application from restarting.
In this article we will try to tell you how to end a user session, what tools an administrator has in his or her arsenal to complete this task, which termination options are provided by the file version and which by the client-server version of 1C.
It is important to remember that forcefully terminating a session may result in data loss. So, to avoid unpleasant situations, it is advisable to warn users in advance about the disconnection.
Closing sessions from the configurator
When changes are made to the database structure, dynamic configuration updates are no longer available. And an information window appears on the screen (Fig. 1).
The sequence of actions in this case is obvious:
- You must click the “End sessions and repeat” button;
- Wait for the database restructuring window;
- Click "OK".
It should be noted that changes made to the program code do not require users to shut down, but they will not work on that device without restarting the application on each specific computer.
Ending sessions directly from the program
Most standard 1C products, version eight, have a mechanism that allows you to easily terminate a user's work remotely and provide the administrator with exclusive access to the database. This is the “Blocking connections to infobase” processing.
You can find it at one of two addresses:
- In one of the submenus of the “Service” section;
- Going to the Operations->Processing section.
Fig.2
The appearance of the processing is shown in Fig. 2.
Features of this processing:
- Checking or unchecking the box and clicking the Record button turns user blocking on and off, deleting sessions and preventing new connections from being created;
- The blocking end time cannot be empty or less than its start time;
- If the “Permission code” parameter is specified, it can be entered into the startup line to ignore the blocking by specifying “/UC” before the code;
- If you do not specify the “Permission Code”, then it will be problematic to get into the database before the blocking period expires (in the file version of work, you can try to delete the 1CVcdn file from the database folder);
- If instead of the parameter “/UC” and a password separated by a space, you specify “/CAllow Users to Work”, where C is Latin, you can completely disable blocking for all users;
- Clicking the “Active Users” button opens a window with a complete list of users (Fig. 3), from where you can open the “Registration Log” or end the session of each specific user.
Fig.3
The two options above work fine in both file and client-server mode. Further we will consider cases typical only for server work.
Removing users from rdp
It is important to remember that disconnecting user sessions from servers is only possible if you have certain rights to do this.
When working from a remote desktop, you can end user sessions using the standard task manager. Simply interrupting sessions is a little incorrect, but quite effective.
The second option is to use the task manager - remote connection with the ability to control each specific session and exit the program according to all the rules. This method is long, and no one guarantees that while one user is logging out, the program will not be launched by any other worker.
Removing users via the server console
Having Administrator rights for a 1C server cluster, you must:
![](https://i2.wp.com/blog.it-terminal.ru/wp-content/uploads/2017/06/Screenshot_21.png)
Very often, when working in server mode, hung user sessions are not visible through the platform tools; they can only be deleted through the console.
The most radical way to interrupt sessions
A situation where the above methods do not work is extremely rare. But if it occurs, there is another radical way to interrupt connections to the database: physically reboot the server.
Of course, users who did not have time to finish their work and save the data will be extremely outraged by such a shameless attitude, but it is fast and it is extremely effective.
The essence of the problem is that viruses replace registry keys and files necessary for user initialization and loading the desktop. Almost any Reanimator LiveCD boot disk will help us fix the first and second. This is a stand-alone operating system that boots directly from a CD (or flash drive) and includes a set of programs for working with a guest computer. In particular, we will need a registry editor. You can download the LiveCD image from any more or less popular torrent tracker. I hope there should be no problems with writing the image to disk either. I'll probably write how to do this in future articles. For now, we will assume that we have already booted from the LiveCD. We will also need the following files: winlogon. exe, userinit. exe, logonui. exe, taskmgr. exe, explorer. exe. They can be found on the Windows installation disk or copied from another computer, for example to a USB flash drive.
So, let's start restoring the system:
1. Using a file manager (Explorer, Total Commander, MidnightCommander, etc.), open the “C:” drive and delete the contents of the System Volume Information folder. This folder stores old “snapshots” of the system with copies of system files. By deleting the content, we eliminate the possibility of restoring any malware that may have remained there.
2. Delete the files (which exist) from the C:WINDOWSsystem32dllcache folder:
In this folder, Windows stores copies of system files in case of system failure, but viruses could replace them.
3. It is necessary to overwrite (with replacement) previously prepared files:
C:WINDOWSystem32winlogon. exe
C:WINDOWSsystem32userinit. exe
C:WINDOWSsystem32logonui. exe
C:WINDOWSsystem32taskmgr. exe
C:WINDOWSexplorer. exe
4. In the “Start” menu, find the registry editor (usually in the “Tools” folder) and launch it. In the registry editor, go to the section:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon
On the right side of the editor we find the following parameters:
Shell – double-click on it with the left mouse button and a window for editing the parameter will open; if it’s different, correct it in – explorer. exe
UIHost – should be like this – logonui. exe
Userinit - should be like this - C:WindowsSystem32Userinit. exe, (with comma).
VmApplet – should be like this – rundll32 shell32,Control_RunDLL “sysdm. cpl"
5. Go to the section:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options
Find and delete (if any) subsections: userinit. exe and explorer. exe
6. Go to the section:
HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionDevices
If there are string parameters (REG_SZ): explorer. exe and userinit. exe - delete.
After these steps, reboot the computer, the system should start with the desktop.