Help - Search - Members - Calendar
Full Version: Terminal Services
UBCD4Win Forums > Other Support > Plugin Repository & Commercial software support
fuderyuu
Greetings,

In this topic rdsok asked what the default login and password are for the UBCD4Win images because he wanted to log into a remote machine using VNC. fourwheeldrifter later responded that RDC is only a client, not a server/service as described here:
QUOTE(rdsok @ Nov 28 2006, 02:29 PM) *
QUOTE(fourwheeldrifter @ Nov 28 2006, 03:35 PM) *
ok is there a default username and password for UBCD4WIN or does that have to be setup? i assume there must be a default admin account


Remote Desktop is provided to connect to other computers... not for other computers to connect to UBCD4Win. The settings that are needed would be ones that are for the system you connect to.. the ip address, username/password and if needed domain name.

What about Terminal Services though?
I created a UBCD4Win about 4 months ago in order to help me with ghosting images and I have been very content with it. However due to my physical location at work, and the locations of the other buildings I manage systems for, it has now become very clear to me that it would behoove me to simply hand out UBCD4Win cds to trusted individuals in each location and have them simply insert the cds for me and I could take over via RDC. I tried this and soon came to realize that the default UBCD4Win image and my WinXPSP2 cd that I used to create my CDs do not have a default Administrator account password associated with that account. I was able to get as far as having the remote computer (the one booting up on UBCD4Win) respond to RDC and ask for authentication... so I know that Terminal Services is running in the background of my UBCD4Win.

My question here is how do I create a new image that has a pre-installed account with Administrative rights and a password into UBCD4Win?
pcuser
You can use this command to add Administrators to the System group:
CODE
net localgroup administrators /add system


I'm not 100% sure but I think it might do what you're wanting. Let us know if it works and I'll let you know how to have it ran at startup.
hilander999
A large portion of the requirements for XP's native Terminal Services to work are included in the systemcore that I designed for version 3.x, however I must point out that NO ONE has actually been able to get TS working in any bartpe or WinPE environment do to the limited system calls that are assumed by adding the /minint switch to txtsetup.sif which is the key to booting from read only media and creates a stalemate when it comes to enabling a fully functional TS Server.

There are many remote applications that have working plugins (some are included) and will do what you need, so how to proceed is up to you. What you are asking is a verry speciffic task and you may have better luck searching over at www.911cd.net/forums as they have a much larger user base and this topic has been discussed in great detail many, many times.

Don't hesitate to ask more questions here if you need help modifying things for your speciffic needs but please make sure your company has enough copies of XP to account for the number of copies of any bartpe build that you hand out just to keep things kosher with MS.

I hate saying this, but as a responsable member of this development team I need to make sure that we keep everything legal, at least on our end. No responce from you (or any one) is required about the licence thing, it just needs to be posted every once in a while to cover us in the event of a lawsuite.

BACK ON TOPIC.
If Terminal services is actually working (have not tested this) it would be cool, but bein the person that designed the core I certainly believe that you will need a third party application to handle this & will still need to add the account information like pcuser posted. I'm pretty sure that part is correct and like I said, check out 911 and I'm sure you'll get something working with little effort once you find the right thread. There is no wrong way to do things like this so it's going to be whatever seems to work best for the situation you have at your place of work.

THANX & Good luck.
fuderyuu
QUOTE(pcuser @ Jan 22 2007, 04:00 PM) *
You can use this command to add Administrators to the System group:
CODE
net localgroup administrators /add system


I'm not 100% sure but I think it might do what you're wanting. Let us know if it works and I'll let you know how to have it ran at startup.

So what will having the System account added tot he Administrator account do? I honestly can't see how that will work. I am not on a station to test it out but I thought I would ask for a bit more of a technical clarification until I can do so so that I can proceed.

QUOTE(hilander999 @ Jan 22 2007, 04:53 PM) *
...There are many remote applications that have working plugins (some are included) and will do what you need...

Can you please provide an example. I am still new to UBCD4Win but I'm a quick learner.
As for the licensing issue, no worries there, I work for a state institution and yes we have more than enough licenses to cover these UBCD4Win CDs.
hilander999
It's not my area of expertise but I believe that both VNC Server & Ultra VNC can allow you to log on to the remote system that is booted with bartpe. Any PE build uses the "SYSTEM" account when booting, adding other account names allows you remote access in certain situations. Yes I know that is rather vague but once again this is not what I work on so we will be waiting for someone else to voice there opinions for you.
jasee
Commercial versions of ghost (now called live state recovery) for the enterprise use a pe environment cd in which they use a thin client version of PC anywhere which you can login to from PC anywhere. This works well. If you use pc anywhere in your organisation in might be useful if you could try making a suitable client as a plugin.
bspolarich
I have a similar need.

I have clients at two remote sites in other states. Occasionally I need to reimage systems. I like BartPE but UBCD4Win is even better. :-)

What I want to accomplish is this:

1. Put CD in system and boot off of CD.
2. Have networking start automatically via DHCP and connect to the "Images" network share at each site.
3. Start VNC Server.
4. Tell the user the IP address of the booted system in an obvious way.
5. Then I can connect via VNC client, and take over from there.

I have #2 working okay, although I'd like networking to start without any user intervention.

#3 doesn't seem to be working yet. I had to start RealVNC server manually and it didn't have a password set. UltraVNC doesn't start because the server service isn't running.

#4 requires some automation.

Would someone be willing to give me a little bit of guidance in how to accomplish this?
hilander999
Do some searching on this site as most of your questions have been discussed in great detail already.

As for #4, I think you should try running COOLMON. I know we were playing with the settings and profiles for it, just not sure what made it into the final release. With coolmon you can display all sorts of information on the desktop, which I believe would be "An Obvious Way".

#2 can all be done through configuring PENETCFG. Take a look at the plugin for it and there is a txt file in the same directory that tells what all values can do. pcuser has answered most of these questions in the best detail, so search by "Show Posts" and not "Threads" so you can find the information easier.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.