Absent Member.
Absent Member.
661 views

Policies for Windows 2008 R2 managed nodes

Jump to solution
Now that I have my OMW8.16 seeing and installing to Windows 2008 R2 nodes, do I need any HotFixes?

No additional policies get deployed to the node other than
WINOSSPI-MSWINApp_Autodiscovery
WINOSSPI-MSWINSys_AutoDiscovery
WINOSSPI-MTS20_FwdAllApplWarnError
WINOSSPI-MTS20_MSDTC.

JON
Labels (1)
0 Likes
1 Solution
11 Replies
Absent Member.
Absent Member.
Thanks, I seen that document but did not notice the HotFix near the end. HotFix has been requested.
0 Likes
Absent Member.
Absent Member.
OK, I installed that patch and deployed another Win 2008 R2 node, same results, only the 4 policies.

Are there policies that need loaded to the management server specific for Win 2008? As I traverse down through the Microsoft Windows policy tree I only see Operating System -> MS Windows 2000, XP and 2003 -> Diagnostic. I dont see anything specific for 2008 or 2008 R2. I have several Win 2008 nodes deployed and they do get many of the WINOSSPI policies.
0 Likes
Cadet 1st Class
Cadet 1st Class
Hello

Check if auto-deployment is enabled correctly for the node?

Regards
Ram
0 Likes
Absent Member.
Absent Member.
Autodeploy is enabled, and the four mentioned policies do get autodeployed, as well as my custome defined policies. it is just that nothing else gets deployed for the WINOSSPI. At a complete loss as to why.
0 Likes
Cadet 1st Class
Cadet 1st Class
Hello

I am assuming that you have already installed the hotfix associated with QCCR1A96343.

If yes then do the following and see if that helps:

1. Undeploy the two auto-discovery policies from the Windows 2008 R2 node.

2. In the OMW Console, use Service Configuration Editor and remove the entries in service map for this Windows 2008 R2 node (only this node).

3. Deploy the two auto-discovery policies again to the node.

Check if the service map gets updated again with details about this node and hopefully with that it will trigger auto-deployment of additional policies to the node.

Hope this helps.
Regards
Ram
0 Likes
Absent Member.
Absent Member.
Didnt help, I tried it twice. The first time the Service->Systems Infra->Windows->Windows Server 2008 R2 Enterprise reappeared. The second time it did not.

Is there anything else with that HotFix? The only thing it does is replace one file "WINOSSPI_CreateServices.js", per the readme.
0 Likes
Absent Member.
Absent Member.
Final lines of the system.txt...

0: ERR: Thu Nov 11 08:29:04 2010: ovcd (5920/3036): (ctrl-27) Error executing BBC RPC action: (bbc-430) HttpOutputRequestImpl::ProcessRedirection(): HttpStatus::ServiceUnavailable case : caught OvXplNet::ConnectionRefusedException_t exception. throwing (ConnectionRefusedExceptionAfterConnectionShutdownAndDelete). There is no server process active for address: 'https://localhost/com.hp.ov.agtrep.notificationreceiver/bbcrpcserver'..
0: INF: Thu Nov 11 08:29:17 2010: agtrep (2472/6536): (agtrep-0) Added Service Instances : WINOSSPI:App, WINOSSPI:TransactionServer, WINOSSPI:TransactionServer20@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:WTS, WINOSSPI:WTS@@ddcb9ca2-5827-754b-1fa9-b8e185688667,
0: INF: Thu Nov 11 08:29:21 2010: agtrep (2472/6084): (agtrep-0) Added Service Instances : SystemServices@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:DHCP@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:Hardware@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:LocalPrinting@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:MSWindows, WINOSSPI:NT:CPU@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Memory:Cache@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Memory:Paging@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Memory:RAM@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Memory@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Networking:DHCP:Client@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Networking:RAS@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Networking@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT:Storage@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:NT@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:Security@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:SystemServices@@ddcb9ca2-5827-754b-1fa9-b8e185688667, WINOSSPI:Windows:6.1,
0 Likes
Cadet 1st Class
Cadet 1st Class
Hello

You may want to talk to HP Support about this auto-deployment issue.

Regards
Ram
0 Likes
Absent Member.. Absent Member..
Absent Member..
while you are deploying the policies, open this node and monitor the ovconfd process, and once the deployment failed, check if the ovconfd process is aborted or not
0 Likes
Absent Member.. Absent Member..
Absent Member..
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.