locked
Sequenced Application's custom event log RRS feed

  • Question

  • Our app creates it's own Event Log, 'Applications and Service Logs\[App Name]' when installed locally. When running the app packaged as an AppV app, the log is not created and the events end up under 'Windows Log\Applications'.

    Is it possible to get the application to write to it's own event log under AppV 5.1 ?

    Monday, August 15, 2016 3:32 AM

Answers

  • Create an add-appvclientpackage script script which creates the log on the local client. The sequenced application will be able to write into the local eventlog.
    I used the same technique for a package I created in the past:
    	<MachineScripts>
    		<AddPackage>
    			<Path>"C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe"</Path>
    			<Arguments>-ExecutionPolicy RemoteSigned -WindowStyle hidden -Command New-EventLog -LogName "Application" -Source "custom_app_name"</Arguments>
    			<Wait Timeout="0" RollbackOnError="false" />
    		</AddPackage>
    	</MachineScripts>
    The above script is an example to create a source inside the applicationlog. You could expand this to first create the Logname too.

    Roy Essers



    Monday, August 15, 2016 9:39 PM