Service Desk Knowledgebase: Windows

From Computer Laboratory System Administration
Jump to navigationJump to search


This is the Windows content page of the CL Wiki Service Desk Knowledgebase. Its purpose is to provide information to the Service Desk team on how to handle problems and requests about this CL service. If you are involved with the provision of this CL service please feel free to add to the knowledge about that it.

If CL staff need to tell the Service Desk team about problems with this service please email
sys-admin-aside@cl.cam.ac.uk.

Return to the Service Desk Knowledgebase SERVICE PORTFOLIO

Key Service Description & URLs

CL Customer Documentation

Further CL Sys-Admin Documentation

Underpinning Services

  • ??? - Any supporting or underpinning services

Customer-base for this Service

  • All staff and students of the Computer Laboratory
  • The admin and support staff have Windows boxes in the main

Costs

  • Free to all current staff and students of the Computer Laboratory

SLA

  • N/A

Service Desk Call Handling Procedure

  • RT tickets can be escalated to the win-admin team by changing the Queue to win-admin with the Owner set to Nobody and the Status set to New. Tell the requestor:
    I am passing this request over to our Windows Admin team who, I'm sure, will be in contact shortly.

Contacts

Primary

Other

Availability

  • Monday:
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday:
  • Saturday: Closed
  • Sunday: Closed

Additional CL Staff Resources

  • ???

Hints, Tips & Known Issues

Finding out a machine's operating system

Graham Titmus (26/05/15)

Whilst it's only the best guess you can try logging into laira and running the command:
cl-hosts -p MachineName
to find out what operating system a machine is believed to have.

Enable remote login to Windows

Graham Titmus (23/01/15)

To achieve this the machine needs to be moved onto an Active Directory (AD) Organisational Unit (OU) called RDP Self Manage.

  1. First read and act on RDP access
  2. Using remote desktop connect to the AD controller adsrv01.ad.cl.cam.ac.uk and login with your admin ID.
    [NOTE: if your machine doesn't have network access to the CL you will need to RDP to ts01.ad.cl.cam.ac.uk and then RDP to adsrv01.ad.cl.cam.ac.uk from there using Start > All Programs > Accessories > Remote Desktop Connection]
  3. Start > All Programs > Administrative Tools > Active Directory Users and Computers
  4. Select View and tick Advanced Features
  5. Click on ad.cl.cam.ac.uk in the left panel
  6. From the menu select Action then Find...
  7. Set Find: Computers with In: ad.cl.cam.ac.uk
  8. Set Computer name: to the name of the machine that needs remote access and click [Find Now]
  9. Right-click on the machine and select Properties
  10. Select the Object tab
  11. In the Cannonical name of the object you can then note which OU the computer is currently in (typically Computers (SUS CL) or AdminMachines) - it needs to be moved to an RDP self manage sub-folder that is within that OU.
  12. Click [Cancel]
  13. Right-click on the computer and select Move...
  14. In the menu that pops up expand the tree below the computer's current location and select the appropriate RDP self manage sub-folder then click [OK]
  15. Close the Find Computers window with [X]
  16. Close down Active Directory Users and Computers with [X]
  17. Logout of the AD controller adsrv01.ad.cl.cam.ac.uk with Start > [Log off]
    [NOTE: and logout of ts01.ad.cl.cam.ac.uk if appropriate]
  18. To take effect the PC will need to contact the Active Directory server which it does about every 30 minutes or be re-booted to make it happen immediately

Change Power Management on a managed machine

Graham Titmus (11/03/15)

  1. Go to Control Panel then Power Options
  2. Select a power option other than Balanced as the default
  3. Modify the settings to set the desired performance, sleep etc.
  4. Close down Power options and Control Panel

Install an Admin machine

Graham Titmus (17/01/17)

Admin machines are installed form the UIS Institution support image over in the UIS. A verion of Office should be installed as part of this process. Once installed on the domain cl.dc.cam.ac.uk the machine should then have its IP address set to one on CL VLAN290. The addresses are taken form the end of the 128.232.30/24 range working downwards. The DNS should be left as that of the Domain.

After the machine is up on the CL network do the following tasks ahead of instaing for the user.

  1. Run \\filer.cl.cam.ac.uk\install\localinstall\IPv6Fix.bat
  2. Register the client with ePO (see install section in [1])
  3. Install printer drivers \\\\filer.cl.cam.ac.uk\install\localinstall\printers\add_drivers.bat
  4. Install relevant printers (see install section in [2])

Categorising Keywords

  • Microsoft Windows PC
Retrieved from "https://wiki.cam.ac.uk/wiki/cl-sys-admin/index.php?title=Service_Desk_Knowledgebase:_Windows&oldid=3439"