[engelby]

Well, I guess just as an add-on to above, instead of about 10-15 clients that need to be rebound, it is now looking more like every computer is going to need to be rebound. I know how to do it remotely, but hopefully this is something they could have messed up just one time, instead of it happening weekly or whatever.

[engelby]

Can anybody explain this in a pretty simple way (for someone that is not the AD guy). They installed SecureID’s here over thanksgiving break and made changes to our AD schema I believe. We have had a lot of re-binding to do today. As an example, every Mac server had to be unbound/bound. All of our servers have never had the need to be unbound and rebound before until today, and we also had a few (10-15) clients that had to be rebound as well for them to work. We were getting the error -14006 on the servers.

I saw a few times in here, people mentioned using 10.4.4. We are using up to 10.4.7 right now, with some back at 10.4.5. Is this fixed in 10.4.8, or is this something that can always happen when whatever happened, happens.

So if computer accounts need their passwords changed by GPO, this is to be expected? Are there any other reason’s why all our Mac servers (all set as Connected to a Directory System) had to be rebound to AD. And while I know time will tell, but do you think this could just be a 1 time rebinding?

[Author]

Posts