Use this command in windows cmd to get the last time your server booted up or was rebooted.
C:\>systeminfo | findstr /i boot
System Boot Time: 10/5/2016, 1:13:08 PM
Boot Device: \Device\HarddiskVolume2
As to who rebooted it ;). You can search the system event log for events with id 1074.
Showing posts with label Windows Server Operating System. Show all posts
Showing posts with label Windows Server Operating System. Show all posts
Wednesday, October 5, 2016
Tuesday, September 16, 2014
MSI installation package did not run successfully.
At times you find that some msi installer that you ran did not install successfully.
You can enable MSI verbose logging by running below command and view the logs from %temp% folder.
You will have to add the below reg key to the machine you are installing the msi on.
Run this command in the admin prompt to add the key.
reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer /v Logging /t REG_SZ /d voicewarmup /f
You can enable MSI verbose logging by running below command and view the logs from %temp% folder.
You will have to add the below reg key to the machine you are installing the msi on.
Run this command in the admin prompt to add the key.
reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer /v Logging /t REG_SZ /d voicewarmup /f
Labels:
errors,
installer,
msi,
Windows Server Operating System
Friday, June 28, 2013
Run command promt as sytem user
The following link helps for opening command prompt as a system user.
http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/
http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/
Thursday, January 17, 2013
Running a powershell script as a Scheduled Task
I found this link to run a powershell script using the Task Scheduler.
http://techhead.co/using-task-scheduler-to-run-a-powershell-script/
To create a simple task to copy a directory from one location to another.Open task scheduler and click Create Basic task.Give the name as Copy task. You can specify and select whether you want to run the task only when you login or keep it running whether a user logs in or not. Once that is done then click the Actions tab and click new. Let the Action be as Start a program. In the Settings text box enter this.
%windir%\System32\WindowsPowerShell\v1.0\powershell.exe
And in the Add arguments enter this after replacing the script path.
–Noninteractive –Noprofile –Command "&{Path to your Script}"
Open notepad and edit the Script file. Enter these lines and save it.
copy-item c:\yourfolderpath -destination c:\destinationpath -recurse
You can start the task and check if the copy is happening. Check the folder permissions and don't add any spaces in the directory names if your copy is not working.
http://techhead.co/using-task-scheduler-to-run-a-powershell-script/
To create a simple task to copy a directory from one location to another.Open task scheduler and click Create Basic task.Give the name as Copy task. You can specify and select whether you want to run the task only when you login or keep it running whether a user logs in or not. Once that is done then click the Actions tab and click new. Let the Action be as Start a program. In the Settings text box enter this.
%windir%\System32\WindowsPowerShell\v1.0\powershell.exe
And in the Add arguments enter this after replacing the script path.
–Noninteractive –Noprofile –Command "&{Path to your Script}"
Open notepad and edit the Script file. Enter these lines and save it.
copy-item c:\yourfolderpath -destination c:\destinationpath -recurse
You can start the task and check if the copy is happening. Check the folder permissions and don't add any spaces in the directory names if your copy is not working.
Monday, October 8, 2012
IE9 32-bit crashing.
My internet explorer started crashing one day. And this error was logged in the applicaiton log.
Faulting application name: iexplore.exe, version: 9.0.8112.16450, time stamp: 0x503723f6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x739ae2d4
Faulting process id: 0x4ac
Faulting application start time: 0x01cda5cf238949d0
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: unknown
Report Id: 617f9fb0-11c2-11e2-b050-002713b3ec0b
After lot of surfing and reading through blogs. I stumbled on this solution myself. I was comparing the registry keys from my machine and another one which had IE-9 installed. I found that this key was different.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\Home_Page]. On my machine it was set to an intranet site of our organization.I changed that to http://www.google.com. The internet explorer started working again. On the first launch it still went to the intranet default site. But was not crashing anymore.
Faulting application name: iexplore.exe, version: 9.0.8112.16450, time stamp: 0x503723f6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x739ae2d4
Faulting process id: 0x4ac
Faulting application start time: 0x01cda5cf238949d0
Faulting application path: C:\Program Files (x86)\Internet Explorer\iexplore.exe
Faulting module path: unknown
Report Id: 617f9fb0-11c2-11e2-b050-002713b3ec0b
After lot of surfing and reading through blogs. I stumbled on this solution myself. I was comparing the registry keys from my machine and another one which had IE-9 installed. I found that this key was different.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\UnattendBackup\ActiveSetup\Home_Page]. On my machine it was set to an intranet site of our organization.I changed that to http://www.google.com. The internet explorer started working again. On the first launch it still went to the intranet default site. But was not crashing anymore.
Subscribe to:
Posts (Atom)