Force a RHN client system to update immediately

run  the command /usr/sbin/rhn_check 

Add the -v switch for verbosity in the /var/log/yum..log

Skip Client For NFS username mapping - Win 2008 R2

This was found during my trouble trying to figure out why MS Windows 2008 R2 was mounting an NFS share (From a Linux NFS server) as read only and the multiple hoops you need to jump through in order to configure username mappings etc...Then I found this solution and it works:

Force ClientForNFS to mount a share using a specific UID and GID, and without the need for a user name mapping server, add the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default

Add two DWORD values: AnonymousUid and AnonymousGid and set to your appropriate values in decimal.  For example: if your server has root user & group ownership/perms for its NFS shares, then you would leave the default value of zero "0" for those two DWORD entries.

Then restart the ClientForNFS service. (You may need to reboot the server.)

Skip Client For NFS username mapping - Win 2008 R2

This was found during my trouble trying to figure out why MS Windows 2008 R2 was mounting an NFS share (From a Linux NFS server) as read only and the multiple hoops you need to jump through in order to configure username mappings etc...Then I found this solution and it works:

Force ClientForNFS to mount a share using a specific UID and GID, and without the need for a user name mapping server, add the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default

Add two DWORD values: AnonymousUid and AnonymousGid and set to your appropriate values in decimal.  For example: if your server has root user & group ownership/perms for its NFS shares, then you would leave the default value of zero "0" for those two DWORD entries.

Then restart the ClientForNFS service. (You may need to reboot the server.)