Status for Andrew DeFaria

Laptop and Password Issues

When getting my laptop I was asked to change my password so the person could login as me and set up my laptop. I did this. After completing the laptop setup I attempted to change my password back to what it was before. This failed. I then tried to change my password to something else. This also failed. I called Helpdesk and they set my password to Summer1 and told me to log out and back in and I should be prompted to set my password. I did this but was not prompted to set my password. So I hit Control-Alt-Del and selected Change password. I then specified Summer1 as my existing password and selected yet another new, unique password (conforming to the Password Policies, of course). I received the message "The password cannot be changed at this time". Called HelpDesk and they told me that I must wait a while and then I could change my password. Waited a day. Reattempted to change my password. Same message.

Meantime the Clearcase License Monitoring, which is running on my desktop, and the web pages also on my desktop were unavailable while I was rebooting my system and working on this problem.

For your reference I took this opportunity to look up exactly what "The password cannot be changed at this time" according to Microsoft. The article is here. According to it you need to make a change to the Minimum Password Age in Active Directory to change it from Not Defined to something defined (like 0 or perhaps something else).

Genius VOB move

As you know we had difficulties performing the move of EntDataARCH and Core_Automation from the Genius region to the standard environment. This was partly due to having the vobadm password changed on us but it was also partly due to the fact that these vobs were created in a "different" environment, thus leaving us with ownership and permissions problems.

I believe I have a fix. Here's what we need to do.

1. Set up another time where we can perform the move
2. Lock the vobs
3. Remove tag for these vobs in the Genius region
4. Re-move (that's re then move not remove! ) the vobs to rtnlprod01
5. Fix permissions¹
6. Register and re-tag these vobs
7. Unlock vobs
8. Configure clients²
9. Test access

Notes:

1. The permissions fix entails running fix_prot -force -root -recurse -chown vobadm -chgrp .vbs, then register and mktag followed by a cleartool protect -chown vobadm -chgrp -recurse . The first fix_prot fixes the protection on various objects but the second cleartool protect is needed to set the owners correctly.
2. Configuration of the clients should be more than just setting their region, CLEARCASE_PRIMARY_GROUP and clearcase_albd service login properly. It should be a complete uninstall of Clearcase followed by a standard Clearcase installation so that we have a proper and known environment.