TS Guru required!
Author
Discussion

slinky

Original Poster:

15,704 posts

279 months

Tuesday 13th June 2006
quotequote all
Morning folks..

I'm trying to work out how best to sort a solution we're working on at the moment.

The aim of the game is to have full replacement desktop, with 1 logon event.

Win2k3 TS, XP Client, Full 2k3 AD etc etc..

So, how can we go about having 1 logon event on boot that takes a user straight to their TS desktop without having to provide any further credentials?

Let me know if you need any more info!..

TIA,

slinky

BliarOut

72,863 posts

269 months

Tuesday 13th June 2006
quotequote all
Winterms?

slinky

Original Poster:

15,704 posts

279 months

Tuesday 13th June 2006
quotequote all
That was my thought initially... unfortunately, the customer already has a boat load of XP client machines that aren't going to be replaced!

slinky

BliarOut

72,863 posts

269 months

Tuesday 13th June 2006
quotequote all
Do the NIC's in the machines support network booting?

Plotloss

67,280 posts

300 months

Tuesday 13th June 2006
quotequote all
You can change the windows shell to be whatever program you like through the registry.

So rather than it start explorer.exe in desktop mode you could start the ICA client, effectively turning the fat client into a thin client.

Then LDAP/SSO on the TS to control application access.

Perhaps?

slinky

Original Poster:

15,704 posts

279 months

Tuesday 13th June 2006
quotequote all
Plotloss said:
You can change the windows shell to be whatever program you like through the registry.

So rather than it start explorer.exe in desktop mode you could start the ICA client, effectively turning the fat client into a thin client.

Then LDAP/SSO on the TS to control application access.

Perhaps?


I like your thinking sir!

Any more ideas are very welcome.. but I'm going to start investigating this one!

Ta!

slinky

JamieBeeston

9,294 posts

295 months

Tuesday 13th June 2006
quotequote all
You know you can 'save' a Remote Desktop session details.


start
run
mstsc

enter all the details (username and password included), then save them to a file.rdp

Then, just stick this in the startup folder of the user, set it to run maximised, and bobs your uncle..

machine boots and loads the RDP session, auto logs in and there you go!

J

slinky

Original Poster:

15,704 posts

279 months

Tuesday 13th June 2006
quotequote all
This would be an option if there wasn't potential for the user to change their password!

Cheers for the idea though chap..

slinky

aldi

9,292 posts

267 months

Tuesday 13th June 2006
quotequote all
slinky said:
This would be an option if there wasn't potential for the user to change their password!

Cheers for the idea though chap..

slinky


Just remove the XP login - set XP to autologin to a non-privilaged account via the winlogon reg. key, put the .rdp file in startup and then the single login can be the TS login rather than the XP login.

spitfire-ian

4,243 posts

258 months

Tuesday 13th June 2006
quotequote all
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?

iaint

10,040 posts

268 months

Tuesday 13th June 2006
quotequote all
spitfire-ian said:
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?


Assuming the remote PC is configured to accept the reomte login. Don't think XP Home will allow remote connections without hackery though.

neil_cardiff

17,113 posts

294 months

Tuesday 13th June 2006
quotequote all
iaint said:
spitfire-ian said:
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?


Assuming the remote PC is configured to accept the reomte login. Don't think XP Home will allow remote connections without hackery though.


Single user only on XP pro too.

Logs out the current user as well - next to bloody useless...

Plotloss

67,280 posts

300 months

Tuesday 13th June 2006
quotequote all
neil_cardiff said:
iaint said:
spitfire-ian said:
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?


Assuming the remote PC is configured to accept the reomte login. Don't think XP Home will allow remote connections without hackery though.


Single user only on XP pro too.

Logs out the current user as well - next to bloody useless...


In a commercial environment, bloody handy if you have a number of machines at home though...

J_S_G

6,177 posts

280 months

Tuesday 13th June 2006
quotequote all
neil_cardiff said:
iaint said:
spitfire-ian said:
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?


Assuming the remote PC is configured to accept the reomte login. Don't think XP Home will allow remote connections without hackery though.


Single user only on XP pro too.

Logs out the current user as well - next to bloody useless...



Quite handy when I'm upstairs in bed and can't be arsed going to one of the downstairs laptops to do some work. Especially if it's something that's a total memory hog (bedroom laptop only has 768mb RAM)/something I've not got round to installing.

iaint

10,040 posts

268 months

Tuesday 13th June 2006
quotequote all
neil_cardiff said:
iaint said:
spitfire-ian said:
Sorry for butting in but I was having a conversation with a colleague the other day about Remote Desktop. Can it be used to access PCs across a network and not just servers?


Assuming the remote PC is configured to accept the reomte login. Don't think XP Home will allow remote connections without hackery though.


Single user only on XP pro too.

Logs out the current user as well - next to bloody useless...


We have fun and games with that one here sometimes. there's something about the way the dialogue asking you if you want to nuke the other session that, if you're not paying attention, means you kick the other user off half the damn time.

As we mainly use it on a box we run tediously slow batch processing on you can imagine the tears!