Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Imported converted standards from ESM has different Target Types to allow data collection

Updated: 26 May 2010 | 2 comments
charliechye's picture
0 0 Votes
Login to vote

Hi there, I have migrated the ESM policy to CCS standards and imported into CCS. The issue I face is the Target Types of the imported standard is being recognized as "Windows 2003 ESM Agents Machines". It seems that that is how CCS decide whether to show that standard to be selected when going through the Data Collection Wizard. While I can see the usual CIS standard that caters for Windows 2003 Server in Data Collection wizard, these imported standards won't appear as an option (basically I think it is because the Machine Types of the asset is Windows 2003 Server). How can I make sure these standards appear when doing data collection for Windows Servers? Feel free to correct my understanding.

Appreciate any sharing. Thanks!

Regards
Charlie Chye

discussion Filed Under:
Group Ownership:

Comments

kevin_stultz's picture
23
Nov
2009
0 Votes 0
Login to vote

CCS ESM Standard

Charlie,

The tool creates a CCS ESM Standard which means it can process data from ESM.  It does not create a CCS "BV-Control" Standard.  The two technologies took different approaches thus converting an ESM policy to a CCS "BV-Control" Standard automatically with a tool is not possible.

CT-219's picture
24
Nov
2009
0 Votes 0
Login to vote

Agree with Kevin

The ESM imported standard will utilize ESM agents as the data provider as opposed to the RMS console. CCS is now capable of accessing the ESM infrastructure to gather data, but will not convert standards. You would need to manually recreate the standard in CCS for it to utilize the CCS Data Collection architecture.