Testing an ICT system

[monkey7]

Well I've basically been hired to test the new remote desktop system of my university.

Sooo I need things to test. Is there anything notorious for not working on remote systems? I'm on an XP machine connecting to an external XP machine. So far I've only found out that the USB sticks are very slow, but I still have 1h30m to torture it.

 

[JN]

Pull the power out the back of the machine you're working on and then see if it will let you reconnect to your previous session when you reboot the PC

 

[Rastalovich]

Print something.

 

[monkey7]

Print works, I don't have access to the follow-me (network printer) though, just a local one.

That power thing is going to happen after our coffee break

 

[JN]

How about firing up something like Excel and slap in a formula that will take ages to calculate thus eating up lots of CPU. See how that affects the performance of other workstations logged in?

 

[Freak]

network printing can be a pain.

 

[monkey7]

The session is stored for about 15 minutes, tried that by hardclosing the session. CPU usage is limited per client, so no one got ****ed when loading the cpu

Getting another three sweet hours this thursday, so keep the suggestions coming

 

[f0x.]

try restarting a service on a remote machine, and also try using the clipboard, it loves to bugger up, a fun one to do is to remote onto another machine from that machine

 

[deathwish]

and then remote into your machine from there

 

[nathan]

try restarting a service on a remote machine, and also try using the clipboard, it loves to bugger up, a fun one to do is to remote onto another machine from that machine

i should hope he doesnt have access to the services (although he may if he's testing).

transfering files from usb to remote session will only be as quick as the network traffic allows it to be.

any idea what there using to limit the cpu usage? guessing its not normal terminal services?

citrix? xen?