Jump to content

Windows 2008 R2 Server Core Installation


Marius
 Share

Recommended Posts

  • Administrators

Pulseway can be installed on Windows 2008 R2 Server Core Installation.

Before installing Pulseway you will need to download and install .NET Framework 4 for Server Core from:

http://www.microsoft...s.aspx?id=22833

Instructions

  • Important: Make sure that your computer has the latest Windows service pack and critical updates. To find security updates, visit Windows Update.
  • If you are installing on Windows 2008 Server R2 on Server Core, you need to install Windows 2008 Server R2 SP1 and follow the instructions below before you install .NET Framework 4
    • Turn on WoW64: Start /w ocsetup ServerCore-WOW64
    • Turn on .NET 2.0 layer: Start /w ocsetup NetFx2-ServerCore
    • Turn on .NET 2.0 layer for WoW64: Start /w ocsetup NetFx2-ServerCore-WOW64
  • On this page, locate the Download button and then click it to start the download.
  • To save the download to your computer so that you can install it later, click Save.
  • To cancel the download, click Cancel.
  • After installing .NET Framework 4 on Windows 2008 R2 SP1 Server Core, it is highly recommended you install critical .NET Framework 4 updates available on Windows Update.

System requirements

Supported Operating Systems: Windows Server 2008 R2 SP1

  •  
  • Windows Server 2008 R2 SP1 Server Core or later
  • Supported Architectures:
  • x64
  • Hardware Requirements:
  • Recommended Minimum: Recommended Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) with 512 MB RAM or more
  • Minimum disk space: 2 GB (32 GB or greater required for OS)
Link to comment
Share on other sites

  • 3 months later...

Hi

The instructions applies also to Hyper-V Server 2008 R2

After the installation of .net framework 4 you can install PC Monitor

msiexec /i PCMonitor_x64.msi

after that, you can start

c:\Program Files\PC Monitor>PCMonitorManager.exe

and configure it as you will and start the service.

Really nice! :-)

Link to comment
Share on other sites

  • 3 months later...
  • 7 months later...
  • 11 months later...

I have a Windows 2008 R2 Server Core running Hyper-V.  I first installed the app on the Virtual Server and it works like a champ, great.  I figured it would make more sense to install it on the Server Core however I'm having some problems.  I've installed .NET Framework 4 and all of the Windows Updates.  

 

I then execute msiexec /i pcmonitor_x64.msi 

 

From there I receive a mid-install error:

 

"There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run.  Contact your support personnel or package vendor."  

 

Ideas?  Thank you.

Link to comment
Share on other sites

Can you please check to see if the msi file downloaded correctly and is not corrupted also make sure you are trying to install the correct msi that is for your CPU architecture.

Sure did.  Just to be sure I tried both x64 and x86 msi files.  I doubt they're corrupt as the x64 did work just fine for a Server 2008 install.  Just trying to figure out what I'm doing wrong for the server core CLI install.  msiexec /i pcmonitor_x64.msi 

Link to comment
Share on other sites

UPDATE:

Well I made a little headway.  I ran msiexec /a pcmonitor_x64.msi and it did install but when I open the interface it says "The service is not installed."  I then went ahead and attempted a msiexec /i pcmonitor_x64.msi which returned the same error:

 

"There is a problem with the Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor."

 

I do have two identical systems running Core and both give the same error message.  Is there a reason the Service is not installing?  Please advise.

Link to comment
Share on other sites

You could manually install the service.

 

Installing PC Monitor Service:

cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319
InstallUtil.exe "C:\Program Files\PC Monitor\PCMonitorSrv.exe"

Extract from manual installation guide.

 

Paul.

 

THANK YOU!  I really appreciate your willingness to hang in there.  It looks really good on my phone.  I got my own rig running for fun and I will feel better now while on vacation.  Going to test the Wake Up feature later on.  Again, thank you.

 

Matthew

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Similar Content

    • By Tim Hall
      After receiving a verification on my phone I get this nasty gram.
       
      So far:
      .Net 4.0 install was blocked because a later version was already installed. So I don't think it is a .net version issue.
      Any help would be appreciated.
       
      --Tim

      I blocked out the server name to keep it annonymous
      I blocked out the server name to keep it anonymous. Also, please ignore the localhost:8443 page. It is irrelevant as far as I know.
    • By Canadian Dental Services
      Hi all,
      I recently did a clean upgrade to Windows 10 on 2 WKSTs previously running Windows 7 with Pulseway installed.  I am now at a loss as to how to re-add these units to my Pulseway instance.
      I see they are still showing up in the “Deployment Successful” tab under “Discovery & Deployment”.
      Is there a way to re-add these units without manually installing the Pulseway app on these WKSTs?
    • By devansh.gohil
      I had installed Pulseway and then wanted to delete it but I was not able to find Pulseway in the control panel uninstall feature and so I tried manually uninstalling files but that also did not work. I tried running the .msi installer again but an error came up saying that Pulseway is already installed but it still was not showing up. Please help me with this.
    • By Wisecompany
      After playing around in my trial account for a bit, I have a few suggestions regarding policy configuration.
      Allow the creation of policies that inherit settings from other policies and track which settings were overridden. This would allow MSPs to create one or two "Global" policies (Servers/Workstations) as a base, and then create individual policies (for each client) that inherit settings from those global policies.  Allow overrides to policy settings on specific systems, track which systems have policy overrides in place, and allow reverting the overrides to the policy defaults. Allow attaching scripts/tasks to policies to run during on-boarding (as in, when the Pulseway agent is initially installed). Instead of having separate Patch Management policies, group those settings with the System policies so they can be applied all at once. Alternatively, allow attaching Patch Management policies to System policies.
    • By sarj2001
      Would love a way to silently install and run Dell command update utility to Dell endpoints to keep drivers up to date, as Dell are frequently rolling out driver updates.
      Has anyone been able to make this work for them? 
      I've looked into it and found some sample scripts on reddit to try and edit and test. the problem I have is getting dell command update to install first, then getting the configuration file out to the required computers that need it, then running the update silently. 
      If someone has managed to get this working, I would love to see how you did it, or kindly ask for some sample scripts to work with?
      Any assistance would be greatly appreciated.
       
×
×
  • Create New...