I am attempting to install the compliance content for 8.2 onto a windows 2008 r2 64bit virtual machine. this machine is also running my console and appserver software and is also my BL file server.
There was no previous installation of complaince content on this machine.
I verified the RSCD agent was running before beginning the install.
I added the installed to DEP.
I verified the RDP settings were compliant w pg 62 of the Compliance Getting Started doc
Delete temporary folders on exit - No
Use temporary folders per session - No
Because this is windows I kicked off Content-Windows-Setup.exe
I Next through the welcome screen
I accepted the License Agreement
I provided BLAdmin & password for a profile w the server name
Credentials passed check
Problem popped up when Appserver validation failed.
Previously I was referred to this KB article:
Which asks you to the following:
* An RSCD agent must be installed and licensed.
oirblgctvwa01# agentinfo oirblgctvwa01
Agent Release : 18.104.22.168
Hostname : OIRBLGCTVWA01
Operating System: WindowsNT 6.1 (x86_64)
User Permissions: BladeLogicRSCD@OIRBLGCTVWA01->nitcadmin@OIRBLGCTVWA01:Privil
egeMapped (Identity via trust)
Security : Protocol=5, Encryption=TLS1
Host ID : 282E5DE4
# of Processors : 1
License Status : Licensed for NSH/CM
* A file server must have, as a minimum, 72 GB of available, non-redundant, disk space. BladeLogic recommends that the file server have 200 GB or more of available RAID 5 disk space.
currently have 79GB of unused diskspace
* A user name must be defined on the file server, and all Configuration Manager users must be mapped to that user. Without this mapping a user may not be able to access a file that another user has stored on the file server. One way to accomplish the necessary mapping is to create an entry like the following in the exports file on the file server:
where <AppServer> is a comma-separated list of Application Server names or IP addresses and <username> is the name to which all users are mapped. To ensure that all users are mapped to the same user, ensure that you do not push ACLs to the file server agent.
from my rsc\exports: * rw,user=NITCAdmin
* The internal System:System role/user must be mapped to the user name defined on the file server. To accomplish the mapping, create an entry like the following in the users.local file on the file server:
where <username> is the name to which all users are mapped, typically bladmin or administrator. If you do not do this and ACLs are pushed to the file server, the application server may fail to start the next time it is started.
from my rsc\users.local: BLAdmins:BLAdmin rw,map=nitcadmin
Nothing appears in the appserver.log or console.log files.