<![CDATA[
<TABLE ALIGN="center" WIDTH="85%" BGCOLOR="#ffffff" BORDER="3" CELLPADDING="15" CELLSPACING="0">
<TR>
<TD WIDTH="25%" ROWSPAN="4" BORDER="0">
<P ALIGN="center"><FONT COLOR="blue" SIZE="4"><B>Navigation Aids</b></font></p><BR>
Filling Out the <A HREF="addhelp.htm">Adding a New User</a> Section<BR><BR>
Filling Out the <A HREF="movhelp.htm">Moving a User</a> Section<BR><BR>
Filling Out the <A HREF="modhelp.htm">Making Changes for a User</a> Section<BR><BR>
Filling Out the <A HREF="delhelp.htm">Removing a User</a> Section<BR><BR><BR>
<A HREF="amdindex.htm"><IMG SRC="go-to.gif" BORDER="0" ALT="Return to..."></a>  AMD Form<BR>
(or use the browser "Back" button)<BR><BR><BR>
</td>
<TD WIDTH="75%" VALIGN="top" BORDER="0"><FONT COLOR="green" SIZE="4">
<A NAME="Add"><P ALIGN="center"><B>Choose "Add new user" when :</b></p></a></font>
<P>the user is new to state employment or comes from an agency outside of DHS. In the first instance, filling out the form will be fairly straightforward since the new user brings nothing with him or her. When transfering from another state government agency, because DHS network and GroupWise administrators do not have access to the user's data on the previous agency's network, it is as if the user is making a brand new start. Although it would be easier for the user to bring data he or she wishes to keep on floppy disks, arrangements can probably be made between the network administrators to transfer files for the user if really necessary. Be sure to add comments to this effect to alert network and GroupWise administrators.</p>
</td>
</tr>
<TR>
<TD WIDTH="75%" VALIGN="top" BORDER="0"><FONT COLOR="green" SIZE="4">
<A NAME="Move"><P ALIGN="center"><B>Choose "Move user from another DHS agency" when:</b></p></a></font>
<P>the user has moved from another DHS agency or branch. The request to move a user is <B>ALWAYS</b> made by the agency or branch receiving the user. Although one could reason that a user transfering from another state agency that uses GroupWise (e.g. ODOT or State Fire Marshal)with a listing in our GroupWise address book under an ORGOVT post office should be moved rather than added, for the reasons mentioned above, adding is the preferred action. DHS network and GroupWise administrators can move all of a user's data, including e-mail, calendar, and documents stored on the user's home directory (H: drive) and even the hard drive of the user's workstation so that he or she need not miss a beat when starting in the new workplace.</p>
</td>
</tr>
<TR>
<TD WIDTH="75%" VALIGN="top" BORDER="0"><FONT COLOR="green" SIZE="4">
<A NAME="Change"><P ALIGN="center"><B>Choose "Make changes to user's personnel or GroupWise" info when:</b></p></a></font>
<P>the user's name, position title or job classification changes so that either the user's network access and/or GroupWise address book information would be affected. Change of one's name due to a change in marital status would be one obvious example. The name change would change the user's login ID (and probably RACF, although that is handled by your agency's RACF security coordinator) and GroupWise account. Promotion within the office would affect only GroupWise address book information. When filling out this section, the "Current" information fields must be filled in so that we can locate the user in the network and then only those fields that are affected by the change; leave the rest blank.</p>
</td>
</tr>
<TR>
<TD WIDTH="75%" VALIGN="top" BORDER="0"><FONT COLOR="green" SIZE="4">
<A NAME="Remove"><P ALIGN="center"><B>Choose "Remove a user" only when:</b></p></a></font>
<P>the user is leaving State of Oregon employment. If the user is transfering to another state agency, especially within DHS, that agency will take care of contacting network and GroupWise administrators to remove or transfer the user's data and anything else required. Remember, the agency receiving the user needs to submit the request to add or move the user.
</td>
</tr>
</table>
</body>
]]>