Last post May 18, 2006 05:27 PM by dfrauzel
May 18, 2006 07:40 AM|SeanWalsh|LINK
I've put together the Consolidated HMC 3.5 build and tested it using some some dummy domains that I have registered. Now that I've got it limping along I want to wipe the DB's and add these back.
Deleting them using the MPSSampleCP changes the status code in the customers table and removes them from Active Directory but when I go to add them back from the CP it says they still exist.
Does anyone know if there is a method to do this without scrambling the rest of the install? I'm not a SQL guy and looking thru the tables see that they are interconencted and keyed to each other so I'm sure it's not as simple as deleting the respective
rows with the data in them.
Any help would be appreciated.
May 18, 2006 02:07 PM|jinesh.shah|LINK
When you delete the organization, it will be only marked as deleted in Database but the entry will not be deleted. This is the way Microsoft has designed it. But according to them, if you create an organization with same properties, it should allow you to
do so irrespective of the older entry as long as its marked as deleted.
Possibly the recipient policy is still existing or the delete method did not clean up everything that it should from ResourceManager database. You might want to check that.
May 18, 2006 05:27 PM|dfrauzel|LINK
Shot in the dark - did you create anything in AD yourself that has the same name as the organization you're trying to create? I discovered early on in using the CP that it relies quite a bit on AD (and ADSI) for its information; I created my own OU under
Hosting, and it showed up as an organization on the CP, and I could even use the CP to edit the users there that I'd created manually using ADU&C. (Except that didn't actually work, of course, since I hadn't created the requisite back-end groups and put them
into _Private, etc.)
Just a guess. For what it's worth, I've found the CP to be very forgiving of mistakes I've made thus far, precisely because it listens strongly to Active Directory, rather than trying to stash everything in its own private database.