Once the K2.net 2003 environment has been updated to K2.net 2003 with SP3, some users may be unable to start and or view processes. The new version of K2.net 2003 includes an optimization for Microsoft Active Directory integration when resolving groups. The loss of rights to start and view processes will only occur if the "Group Name" and the "Group Name (pre-Windows 2000)" in Microsoft Active Directory are not the same.

To correct this, first check that the two names are not the same. If they are not the same then the K2.net Service Manager is used to restore to the users that have lost their permissions their appropriate access rights to start and view processes.

To re allocate the permissions to the group all that is required is to open K2.net 2003 Service Manager, identify the group using the "Group name (pre-Windows 2000)" and then provide the group with the appropriate permissions.

To accomplish this, do the following from the machine where the K2.net 2003 Service Manager is installed:

• Click on "Start > All Programs > K2.net 2003 > K2.net Service Manager"
• Select a K2.net Server e.g. "My K2.net Server > Groups"
• Right click on "Groups" and select "Find Groups"
• Search for groups using e.g. "My" as a search mask. Notice that the group appears in K2.net 2003 Service Manager using the pre-Windows 2000 group name

• Click "Ok" to add the group
• Select the group e.g. "My K2.net Group"
• Right click on the group and allocate the permissions to the appropriate processes
• When complete, click "Ok" and close the K2.net 2003 Service Manager