Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Server Problem

Updated: 22 May 2010 | 3 comments
Elizabeth Beben's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

I hope someone can point me in the right direction for this.



I do not use PXE.



We have two deployment servers on campus, one that I manage (server1), and one that is independent of mine entirely (server2). They usually co-exist peacefully, until yesterday afternoon.



I built a computer from scratch, right clicked on it in my console, and chose "Install Automation Partition." WinPE balked, saying there was no valid repository. I next tried the DOS partition, and it prompted me for the password for server2. I've since checked other computers I haven't imaged lately, and they're all looking for the password from server2.



I checked under Tools > Options, the Agent Settings tab, and "Force new Automation agents to take these settings" was not checked (although I'm certain I've checked it before). I checked it, verified that server1 was the server listed under Drive Mappings, and the correct username/password is listed under Authentication. I rebooted my server and tried to reinstall an automation partition, and they're still looking for a password from server2.



Any ideas what to do next?

Comments

Elizabeth Beben's picture
10
Sep
2008
0 Votes 0
Login to vote

And I should mention that on the properties of these computers, the Deployment Server listed is server1.

Stu Harris's picture
10
Sep
2008
0 Votes 0
Login to vote

One thing you could try is to create an uninstall package and drop that on the these offending boxes to remove the automation partitions. Then once you verify that the automation partitions are gone, reinstall from your server.

Elizabeth Beben's picture
24
Sep
2008
0 Votes 0
Login to vote

I actually figured it out, with a little help from a co-worker. My default.cfg file had changed. I retrieved the file from a backup, and it's working now. I'm not sure how it was changed in the first place, though.