• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Installing smp client before ghost

P

Pogo

2[H]4U
Joined
Sep 17, 2000
Messages
3,744
Ok, so i've got a quick question before I send out the final image on a machine that will be used to ghost 9 others.

I'm installing the smp client as a service as described here on the forums, but I need to know if i'm going to run into any issues with machine id's or anything else. I'm setting up a system that will be used as a master ghost image. However, i'm not doing the imaging, and I also do not know if i will access to the machines after they've been ghosted, at least not anytime in the immediate future. If i get it to the point where it will run as a service properly, but not download any wu, will I run into any issues later on.

I am not running sysprep on these machines. ( i know i know, time constraint keeps me from doing it right) So For all intensive purposes they'll all be pretty identical except for the computer names which i will make the person doing the ghosting handle.

Thanks guys/gals
 
I suggest you put only the client .exe and client.cfg along with the configured service. It's easy as configuring the client, make sure it run fine as a service then delete everything beside these two files, stop the service before you image it (just leave it at auto, just stopped). Upon the next reboot, it will create a new id.

Also, make sure you delete everything in the registry related to the folding client so when it run next time, it will create a unique ID. FLECOM would have the expertise for this.

 
Problem I think you will hit is the MPI installer deally needs the user/password configed in the registry. These are saves as computer/user I think and even if the user name is the same, different computer name and your screwed.

I tried this, I did sysprep the mess I think, and MPI keep hanging up on starting. I had to relaunch the install.bat program to get MPI to shut up.

Just dump the reg key for machine ID, all that is needed there. All you really need locally is the .exe and the .cfg file.

Regarding SMP Configed as a service and all this, I've not messed with that.

I'm pretty sure the MPI permissions will be hosed in the changing of the computer names. Get the guy to rerun the install.bat perhaps and add the credentials back in but that's not very down low...

Plus, the SMP client will expire soon enough anyways so then your hosed.
 
For the SMP client as a service (I somehow missed that), the best way is to create a local admin account with password then register the service with that local account instead of the user account and it will work without too much problems.

 
crap, harder than i thought. and i have to get this machine out the door in 20 mins.
 
well, im gonna give this a shot according to the following:

i've got the client installed, setup as a service, proper adjustments made to the service log on and the registry (added the -forceasm flag)

Haven't yet restarted to make this connect to the internet and download a wu. so its at this state. I will be over at the location this friday and hopefully the machines will already be over there and I can clean up the issues myself.
 
You must log in or register to reply here.
Back
Top