Resource Accounts accessed by automated processes fall into three main groups:

• If you have a Resource Account that you need to "poll," (periodically log in and retrieve email using the POP or IMAP protocol), then you will need a HoldingID to automate the process. Resource Accounts do not have a password of their own, and of course you would never think of embedding your own NetID and password in a script, so this provides you with an ID that you can use explicitly for that purpose. A single HoldingID can be used to access more than one Resource Account.
• If you have email delivered to a process via SMTP, then you do not need a HoldingID. You can tell that you have this case if the address of the automated process appears in the routing for the Resource Account.
• If your Resource Account is directed to a Remedy queue, you will be contacted by the Remedy staff with instructions. Do not follow the steps in this article.

HoldingIDs are created and administered in CornellAD (Active Directory).

Here are the steps needed to use a HoldingID with a Resource Account.

1. The Primary OU Admin for the unit creates the HoldingID. Because a single HoldingID can be used to access more than one Resource Account, choose a name for the HoldingID based on the department or project group, not the name of the Resource Account. (List of OU Admins for most campus units)
2. The Resource Account owner (or the unit's primary admin) submits a ticket to idmgmt@cornell.edu asking to have the HoldingID enabled for Resource Accounts. Then:
   • Identity Management moves the HoldingID to OU CUniv/MessagingObjects/HoldingIDs.
   • Identity Management notifies the customer that the HoldingID can now be used for Resource Accounts.
3. The Resource Account owner or administrators can assign Access privileges to the HoldingID using the Exchange Account Manager.

For a fuller discussion, see our Technical Issues: Resource Accounts and Automated Processes article.