Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

import rules - got one working but need to expand

Created: 25 Jan 2013 | 7 comments

Ok so I will throw a few things out there first to set the tone.. 

We currently have a custom data class with a custom inventory. It works 100% in NS6 and in NS7.1 SP2 MP1

now all is well in NS7.1 world for XP and up OS.... since Win2k is no longer supported I was told that I need to import data from my NS6.
I have never done this before so I set off to do it...

I have most of it working but need some help here.

Trying this on our DEV server..

I was able to filter out the win2k boxes with the Data Filter [OS Name] like '%2000%'

that worked and brought in only 163 machines.

Now our custom inventory I want to bring in doesnt have os name in it...

so when I create an import rule, tie it to the custom inventory it wants to bring in 4300 devices.. err no I dont want all prod comuters brought in only the data for the 2k boxes. how do you filter this out?

not sure what to put as you cant join multiple tables.. since I used inv_aex_ac_identification with data filter [OS Name] like '%2000%' that kept all 4300 out but just the ones i wanted....

when I click show data it brings up the data for the custom inventory. but in the drop down box is the inv_aex_ac_identification.

how do I reference that in the data filter as I would like to put in there... [OS Name] like '%2000%'

do you do this in associations or reverse associations?

thanks guys/gals

Comments 7 CommentsJump to latest comment

TeleFragger's picture

any good links out there explaining how to do this stuff that you guys know of?

looking to filter out what i bring in...

Did we help you? Please Mark As Solution those posts which resolve your problem,

mclemson's picture

So you're using an OBDC data source to connect to your NS6 database after creating a System DSN in ODBC.  I created a simple query that proves there is no problem joining a table in your query:

SELECT vc.Guid,
vc.Name
FROM vComputer vc
JOIN Inv_AeX_AC_Identification aci ON aci._ResourceGuid=vc.Guid
WHERE vc.IsManaged=1 AND aci.[OS Name] NOT LIKE '%Server%'
 
So this should work fine.  Unless I'm not understanding what you are trying to do.  You did create an ODBC data source, right?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

TeleFragger's picture

Sorry I didnt explain it better.. We did not migrate any data from NS6 into 7.

We are upgrading by site and letting all new inventory come in, however Windows 2000 is not supported for the Altiris Agent and I need to at least inventory these machines. As of NS 7.0 SP5 Windows 2000 is not even supported in the Stand Alone Package.

So I created a data connection and imported in Inv_AeX_Ac_Identification where OS Name like %2000% and that worked... I can now report on windows 2000 but to the limited function. Reading up more it seems that you need to keep on bringing in more tables to get more data for the Windos 2000 boxes. So I tried adding a second but wasnt getting anywhere so was looking for a best practice for this kind of thing.

Thanks
 

Did we help you? Please Mark As Solution those posts which resolve your problem,

mclemson's picture

If you need to report on historical data, then just report against the NS6 server from the NS7 server.  The account used for SQL on NS7 must have access to run reports on the NS6 SQL server.

Let's say you needed a list of all Windows computer names in NS7:

SELECT vc.Name
FROM vComputer vc
WHERE vc.IsManaged=1 AND vc.[OS Name] LIKE '%Windows%'

 
If you wanted to also report for those Windows 2000 systems in NS6, you would perform a UNION of two queries. In this case, the queries happen to be almost identical for both databases.  This will almost never be the case, but I happened to pick an easy example:
 
SELECT vc.Name
FROM vComputer vc
WHERE vc.IsManaged=1 AND vc.[OS Name] LIKE '%Windows%'
 
UNION
 
SELECT vc.Name
FROM Altiris.dbo.vComputer vc
WHERE vc.IsManaged=1 AND vc.[OS Name] LIKE '%Windows 2000%'
 
This works given that 'Altiris' is the name of the SQL database and it's on the same SQL server as your Symantec_CMDB database.  If it's on a separate server, it would be FROM servername.Altiris.dbo.vComputer.  You may need to perform additional configuration (as guided by SQL Studio) to get this to work.
 
I used this method to do reporting across an NS6 server used for Windows 2000 and Windows XP and an NS7 server used for Windows XP and Windows 7 at a client.  I wouldn't recommend importing your Windows 2000 into NS7.  Whether it's live or historical, just pull it in real time from the NS6 server.
 
Does this make sense?  Will it work for what you need to do?
 

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

TeleFragger's picture

Thanks Mike.. it will work and makes sense.. will work till next few months when we shut down the NS6 server... frown

Hah... so that is why im trying to import the items into the 7 db... 
I mentioned yesterday that we could P2V the servers (NS6 console and seperate SQL box) and keep them running in the background for the win2k boxes to keep reporting into. This would work and so would your method... 

appreciate it.. gonna figure out what to do next..
 

But still if anyone knows how to do the connector like I did for the one table but to do multiples im still all ears.. devil

Did we help you? Please Mark As Solution those posts which resolve your problem,

mclemson's picture

I'd keep the NS6 running for the Windows 2000 boxes.  It'll help you at some point when you're ready to migrate those to a current OS -- if that ever comes up.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

TeleFragger's picture

lol umm no most likely no convert.. they are running in a laboratory area where some of the vendors are out of business or the pc's connected are expensive and to the software they run so no way to upgrade. we are migrating to win7 now so doing what we can... but yes were trying to get those win2k's to win7....

we even have win9x, and nt machines... hah

Did we help you? Please Mark As Solution those posts which resolve your problem,