Windows 10: Where do i find windows services sessions sessions.xml?

i want to unnistall it but i dont know where it is

:)

 

Sync from a Terminal Services Session?

Environment:

- Windows Server 2003 R2 Enterprise Edition

- Users login to Terminal Services Sessions

- Office 2007

- Windows Mobile devices



We want to be able to sync the Windows Mobile devices from within the Terminal Services Sessions.



Via USB connections on the Local Desktop PC or Laptop?



Via a Network Connection?



Any suggestions are welcome.



Thanks in advance.



db

 

\Windows\Servicing\Sessions - Log bloat?

please try the following steps to reduce the size of the directory:

1. Stop the Windows Module Installer service. This service is responsible for managing Windows updates and servicing, and stopping it will prevent any further changes to the Sessions.xml file and the random-number.xml files.

2. Rename the \Windows\Servicing\Sessions directory to something else, such as Sessions_old.

3. Create a new \Windows\Servicing\Sessions directory.

4. Start the Windows Module Installer service. This will create a new Sessions.xml file and a new set of random-number.xml files.

5. Check for pending Windows updates that may be stuck and causing log bloat. Open an elevated Command Prompt and run the following command: dism /online /cleanup-image /startcomponentcleanup

Keep me in the loop with the result. Thank you.

Best,

Mostafa

 

Local Sessions Manager

Hi Carol,

Thank you for writing to Microsoft community forums.

Did you make any changes on your computers recently?

Are the computers on domain?

Do the computers boot to desktop or get stuck at
"Waiting for Local Session Manager" screen?

Local Session Manager (LSM) is a Win32 service, which starts automatically when the operating system starts. It is a core Windows Service that manages local user sessions. Stopping or disabling this service
will result in system instability.

Local Session Manager cannot be started if the following services are disabled, deleted or working improperly.

DCOM Server Process Launcher.

Remote Procedure Call (RPC).

RPC Endpoint Mapper.

To help you better with this issue, please get back to us with answers to the questions listed above.

Peer Samie

Microsoft Community-Moderator