The security database on the server does not have a computer account for th

[game_over]

I've installed 2 windows 7 machines, both identical.. added them 2 the domain. on 1 of them when someone tries to login they get an error;

The security database on the server does not have a computer account for this workstation trust relationship

restarting the machine and trying again lets them login.. but then will randomly happen again later on, again a restart is all that is needed to allow the login.

any ideas whats causing this? the other identical machine is fine. I'm about to add 31 more to the domain so would like to fix this first.

[sc302 Veteran]

http://www.google.com/#sclient=psy&hl=en&safe=off&source=hp&q=The+security+database+on+the+server+does+not+have+a+computer+account+for+this+workstation+trust+relationship&pbx=1&oq=The+security+database+on+the+server+does+not+have+a+computer+account+for+this+workstation+trust+relationship&aq=f&aqi=&aql=&gs_sm=e&gs_upl=180663l180663l3l181021l1l0l0l0l0l0l0l0ll2l0&bav=on.2,or.r_gc.r_pw.&fp=7d86af9665111856&biw=1229&bih=867

Google has some suggestions for you to look into. But you can start by disjoining and rejoining the domain. Did you image the pc's and use sysprep, you may want to sysprep the machine it makes a lot of changes to the system config to make the pcs unique. Just had an issue of where I deleted 3 of the same pc names in active directory, which in turn removed 3 seperate pcs off the network, and now I am rejoining the pcs after running sysprep on the individual pcs so they no long share the same system identifiers.

[zeta_immersion]

might want to try newssid then readd to domain

[sc302 Veteran]

Not sure if newssid will work on win7. The writer discontinued because he found it to be a myth. Tell that to my current issue...must be a figment of my imagination that this all happened coincidentally.

[game_over]

  On 08/09/2011 at 16:40, sc302 said:

http://www.google.co...iw=1229&bih=867

Google has some suggestions for you to look into. But you can start by disjoining and rejoining the domain. Did you image the pc's and use sysprep, you may want to sysprep the machine it makes a lot of changes to the system config to make the pcs unique. Just had an issue of where I deleted 3 of the same pc names in active directory, which in turn removed 3 seperate pcs off the network, and now I am rejoining the pcs after running sysprep on the individual pcs so they no long share the same system identifiers.

i tried leaving the domain and joining again. i also just used the domain name rather than the FQDN. Didn't image the 2 computers but i do plan on imaging the other 31 (i plan on following this guide: http://magalan.co.uk/Create_a_Custom_Windows_7_Image_For_Network_Installation.html -- would you suggest anything different?)

I will look through the suggestions on Google.

[sc302 Veteran]

That is fine and as long as you did not use the same non syspreped image, I do not see where a dupicate machine could cause the issue that you are having and disjoining and rejoining the domain may solve your issue. however take a look at the options that google has, there seems to be quite a few different scenerios that can fix your issue or be the cause of your issue.