bootlog.pml) and select the "Save" button. Insert in the “File name” field the desired name for the output (e.g. Click “Yes” to save the collected data.A dialog box will appear stating “A log of boot-time activity was created by a previous instance of Process Monitor.Launch ProcMon on your remote workstation.It is important that we copy and not move until we have verified the PML file is correct as ProcMon will delete this file from C:\Windows once conversion in complete Copy the procmon.pmb file into C:\Windows on your remote workstation.Now we need to “trick” our remote workstation’s Process Monitor into opening the procmon.pmb file and converting it to PML.Or, if possible, remotely browse to the file using the C$ share in explorer and copy it to your workstation via File Explorer.We will now need to remotely collect the file C:\Windows\procmon.pmb (This is where Process Monitor is storing the events since boot) from the VDA to a remote workstation You can use PowerShell on your workstation to do this Once machine is available, log in and wait for the issue to reproduce.Select the “OK” button to close the program. Process Monitor is configured to log activity during the next boot.A dialog box will appear stating “Process Monitor is configured to log activity during the next boot”.Now go in to the “Options” menu and select “Enable Boot Logging”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |