So sounds like you have two domains with no trust between them, is that correct? Also, sounds like you just want to have the inventory information (no agent/no manageability) in your core from the machines in the other domain, is that correct? If yes then you can try just doing an agentless scan, something like this:
\\core name\ldlogon\LDIScn32.exe /NTT=core name:5007 /S=core name /I=HTTP://core name/ldlogon/ldappl3.ldz /NOUI /F
The question is how to run this on the machines - login script, lddiscover, psexec, etc...
How will the below script run when there would be no connectivity between the Domain B machines and the Landesk core server (which is in Domain A).
That why I asked the question about trust. So you are stating that there is NO network connectivity between the domains? If that is true, then you will have to run the inventory scan with an /o option to store scans to a central location and then somehow grab the scans (usb drive, dvd, etc...) and dump them in your cores ldscan folder. From the old forum some files may be a little old:
You could just copy your clients ldcleint folder to a share and run ldiscn32 from there. Tricky part is how to get the scans from domain to domain, this may be a manual process. If both have interent access and a public ftp/http site you could upload then download.
Just some thoughts.
If i copy the ldclient folder on that domain and run the script that you had provided on all the machines then where will all the inventory of that machines will be generated i.e. in which file as per the script the output will be generated in "ldappl3.ldz" file. The same file is also present in my core server ldclient folder, need to know if i copy that file in live server folder wont it overwrite my current ldappl3.ldz file which may affect my live scenario inventory. Please suggest on this..
CentralLocation\ldlogon\LDIScn32.exe]/NTT=CentralLocation:5007 /O=CentralLocation /I=HTTP://CentralLocation/ldlogon/ldappl3.ldz /NOUI /F
Is the above script correct??
1 of 1 people found this helpful
\\some location\Ldiscn32.exe /F /O=\\some location\%COMPUTERNAME%.scn
You may have to play with this a little (e.g., cd\, etc...) I've not done this for a very long time. Then again it may not work at all All theory at this point.
Can you tell me how can this %Computername%.scn file be imported into my live server so that it can be viewed in my console.
Or is there any other way i can do this?
All the scn files will have to be somehow (see messages above) collected and copied to you
core server\ldmain\lsdcan folder. The inventory service will then process them into the DB.
should i directly copy the %computername.scn% file to "ldscan" folder. If yes then should i start and stop the inventory scan services after copying and will it affect the present inventory report??
Nope just copy your scn files. THe service will process any scn files put into that directory.
Once the service processes this file, will that machine be shown in the console directly. How much time will it take for this process to function.
I will test this and will update it accordingly.
Yes. You are just doing - manually - what the inventory client (ldiscn32) does automatically. Service should process them very quickly and if they are valid scans will be inserted into the DB for you to see in the Console.
why not put credentials for DomainB into Configure > Services > Scheduler > Change Login > Alternate Credentials, do a UDD scan of DomainB, and then just push agents?
I believe there is 0 network connectivity between the sites.