Now, when you get ready to install, if you don’t need all the other stuff, select the following options. By selecting only the.NET Framework 4.5 Software Development Kit you will get GACUTIL.EXE installed in the C:Program Files (x86)Microsoft SDKsWindowsv8.0AbinNETFX 4.0 Tools folder, at a. Download the spiceworks.exe file to another computer and copy it via the network or usb drive to the Windows Server Core install. Note: Be sure to remember where you copied the install file to. Step 2: Run spiceworks.exe on the server.
Learning has never been so easy!
This will show how to install SpiceWorks on a Windows Server 2012 Core minimal install.
8 Steps total
Step 1: Copy spiceworks.exe to the server.
Download the spiceworks.exe file to another computer and copy it via the network or usb drive to the Windows Server Core install.
>Note: Be sure to remember where you copied the install file to.
Step 2: Run spiceworks.exe on the server.
Using the Command Prompt navigate to the spiceworks.exe file and run it. Once you are finished you will get a .dll error. Just hit OK as this error is related to not having the necessary files to run IE.
>Note: I use a domain username and password to run the service. If you do not wish to do the same omit 'obj= ######## and password= ##########'
Step 4: Open Registry Editor.
Type regedit in the command prompt and press the enter key.
Step 5: Navigate to the SpiceWorks service.
Path to get to the service: HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > SpiceWorks Click SpiceWorks.
Step 6: Edit the Image Path.
Right Click 'ImagePath' and Click 'Modify'.
Change> C:Program Files (x86)Spiceworksbinspiceworks.exe service To> 'C:Program Files (x86)Spiceworksbinspiceworks.exe' service
Press OK
Notice I inserted 'Quotation Marks' around the path leaving out the word service. I have tried to do this from the command prompt while creating the service but it does not go well.
Step 7: Set Error Recovery.
You can configure error recovery using SC or by using services.msc from another computer and connecting to the server.
To use SC type the following: C:>sc failure SpiceWorks reset= ErrorFreePeriod actions= restart/####
Replace ErrorFreePeriod with the number of seconds with no failures after which the count should be reset to 0. Replace #### after restart/ with the number of milliseconds of delay you want before the service restarts.
Step 8: Start using SpiceWorks.
Open your web browser and enter the IP Address or FQDN of the server in the address bar. You are ready to start enjoying SpiceWorks on a minimal install server.
SpiceWorks can fully function on a Core Installation of Windows Server 2012. It may take a few more steps but is well worth looking into if you virtualize or wish to install on a box with limited resources.
References
SC - TechNet
17 Comments
Datil
HenrikBryne Mar 12, 2014 at 07:22pm
Very nice! I'll give this a try as soon as I get the chance. Thanks for sharing!
Poblano
Arcturus08 Mar 12, 2014 at 07:39pm
Thank you! I use this setup at remote locations for site device scanning.
Jalapeno
AndroidChris Mar 13, 2014 at 02:03pm
Very handy how-to, thanks for posting. Simple and effective.
Anaheim
jimwilliams May 12, 2014 at 02:43pm
Many thanks; we want to run two helpdesks (on for IT and one for maintenance) so this will be very useful for setting up VMs on single hardware.
Poblano
Arcturus08 May 12, 2014 at 02:47pm
@jimwilliams
We did the same thing. Also they work great for remote collectors at satellite offices.
Jalapeno
Rodan07 Aug 22, 2014 at 05:34pm
Thanks, awesome how-to, very thorough. Great work Arcturus08. Spicing up!
Serrano
Devildog Oct 1, 2014 at 08:56pm
Great instructions. Installing or Upgrading SpiceWorks you might run into an error message 'Error loading url.dll The specified module could not be found.' IE is not installed on the machine and causing the error. Using another compute launch the main URL of your SpiceWorks installation to finish the installation or upgrade.
Pimiento
kennethsims Dec 22, 2014 at 07:07pm
I used a browser to download spiceworks.exe then installed. Did I need to do all of these steps?
Jalapeno
dzampino Feb 5, 2015 at 06:13pm
As an aside, by default port 80 is blocked so run this from the command line to open up that port: netsh advfirewall firewall add rule name='Open Port 80' dir=in action=allow protocol=TCP localport=80
Poblano
Arcturus08 Feb 5, 2015 at 07:04pm
@kennethsims - Only if you are running Sever Core.
@dzampi - Indeed you do. We use group policy to open the port internally for the Domain profile.
I need to backup and restore my config though. I'll see how I make out.
Datil
Brian Steingraber Jun 1, 2016 at 03:26pm
Has anyone tried installing the Spiceworks Network Monitor on Server Core?
Serrano
Phil6024 Jul 15, 2016 at 09:55pm
Extremely helpful. Has anyone tried this inside a Windows 2016 container?
Cayenne
Techie4Life Apr 1, 2017 at 12:12am
@Phil6024 I have not and was wondering about how to even use containers. I really want to try them out for stuff like this.
Pimiento
itadmin224 Apr 4, 2017 at 12:30am
Just did this on server 2016 core. Seems to be fine. Didn't need to manually create the service. Just run the exe, ignore the dll error and open port 80.