Exporting with 8.5

[Guest]

I have noticed since upgrading to 8.5 I cannot open the export that I usually do every month. another computer has 8.1 and you can open the export txt file without issue. Should have I not upgraded and go back to 8.1? Or is there something I am doing wrong. I typically configure a WMI query for a specific application. I run export pro to put the results in a txt file. and then open the txt file to review the results/use it to compare with assets in our directory.

[cmccullough]

Re: Exporting with 8.5

Give us step-by-step details on what you are doing and what is happening.

[Guest]

Re: Exporting with 8.5

Quote: Originally posted by cmccullough:
Give us step-by-step details on what you are doing and what is happening.

I select a certain number of systems in AD. I create a custom WMI Export Template: output file-C:\Program Files\Hyena\Adobe_Shockwave.txt WMI Where Clause-DisplayName ="Adobe Shockwave Player 11.5" WMI Class name-Win32Reg_AddRemovePrograms
Query Properties-__Server, DisplayName, Version, Installdate
I run the Export and watch it access each computer. When its done it prompts me open the file. I usually select notepad so I can review it and save it in another location for Asset Comparison. From here it will not let me open the file like I have for years. Maybe its not done yet but prompting me to open the file. I dont understand why I cant open the file.

[cmccullough]

Re: Exporting with 8.5

The easiest test you can make to trouble-shoot WMI reporting problems is to remove the Where Clause and run it again to see if you get output that way.

If you still don't get anything, change the output file location to your desktop to see if it is a problem creating the file (permissions, etc.)

[Guest]

Re: Exporting with 8.5

Quote: Originally posted by cmccullough:
The easiest test you can make to trouble-shoot WMI reporting problems is to remove the Where Clause and run it again to see if you get output that way.

If you still don't get anything, change the output file location to your desktop to see if it is a problem creating the file (permissions, etc.)


looks like that was the problem. The default Program files\Hyena, must be an issue. OK I will keep all my exports under my profile where I automatically have full access to. So That means I need to change any previous outputs to a different location. Thanks so much this was a big help!

[kstanush]

Re: Exporting with 8.5

If you are using Windows 7, Microsoft changed security around so that users no longer can normally write to anything under the "program files" directory. Seems dumb to me, but you now have to write to either a directory somewhere else or the profile directory, but that directory level is sometimes cumbersome to access.

[Guest]

Re: Exporting with 8.5

Quote: Originally posted by kstanush:
If you are using Windows 7, Microsoft changed security around so that users no longer can normally write to anything under the "program files" directory. Seems dumb to me, but you now have to write to either a directory somewhere else or the profile directory, but that directory level is sometimes cumbersome to access.


Thanks, we are using Vista and its locked down pretty good. I am sure you have heard plenty of stuff about Vista! Got to Love it

[Guest]

Re: Exporting with 8.5

Heres another, when I schedule a task to run, I select "Now" in hopes it runs immediately and then delete after completed. It usually runs well, but I have to go in afterwards and delete the task. when dealing with a large amount of systems, it can be a little difficult. How can I configure it to delete when done? Or should I not even care that the scheduled task is left there? It looks like it will run again next month at the same time. I do not want it to do that. Whats the best way to run a scheduled task with the least amount of cleanup?

[This message has been edited by zmitchell (edited 02-14-2011).]

[kstanush]

Re: Exporting with 8.5

This is probably a limitation of the task scheduler v1.0 interfaces, which Hyena uses. Vista and Windows 7 now use v2.0, but Hyena does not support that. We are going to have v2.0 support in the next update, probably in a couple of months. We should have a beta version available in about a month. If you want to join the beta group, send a blank email to [email protected]