billcreager2
(Bill C (Spiceworks))
1
7.5.00065
Help Desk
- 67159 - Helpdesk - look into checking ‘alt_profiles’ when new tickets are submitted
- 70388 - Helpdesk Import: the System admin is assigned tickets
- 70872 - Portal not formatting with International Date settings properly
- 71029 - Helpdesk: Remote Site: New custom attributes (or edits) don’t sync from the central server → the remote site until the remote server is restarted
- 71594 - Unable to delete default value on date attributes
- 72016 - Due date not displaying correct value
- 72082 - User Portal: error when submitting custom ticket form with attachment- translation error: [“user_portal.user_content.custom_ticket_form_block.submitting_file_with_attachment”]
- 72187 - Settings - Monitors and Alerts close ticket after problem resolved will not stay set
- 72240 - Ticket Dashboard not displaying for Help Desk Admins
- 72320 - Dates not showing correct value
- 72455 - Dialogue box on ticket-device relation will not collapse
- 72533 - Re-write bulk ticket import and add to UI
- 72702 - Tickets Anywhere Command - Created By: will set value to wrong user, if names are similar
- 72823 - Speed up the ticket dashboard
- 72975 - Ticket Dashboard Not Loading After Upgrade to 7.5.00061
- 74143 - “More” link on ticket description needs to be tranlated
- 74173 - Ticket Dashboard: Labor Time Spent not scoped to correct dates
Inventory
- 28824 - Remote Collectors: enforce remote/central site version match
- 33938 - External Alerts Matching Against Hostname is Case Sensitive
- 61977 - Unselected Device Cards Appearing As Successful in Fix Login Flow
- 62961 - network data dropped on exception, SSH devices
- 64539 - conversion of unprobed device incomplete, devices left in corrupted state
- 65198 - Some HP printers report a real number for “max_level” and a percentage for “current_level” toner values
- 65734 - Table View: Sorting is done alphanumerially
- 66437 - search not working in table view
- 66642 - “Location” attribute from AD Computer Objects not auto-populating.
- 67301 - Devices incorrectly classified as laptops because of attached UPS
- 67369 - CyberPower CP1350AVRLCD 1350 not detected as UPS
- 67581 - Vendor name updates not reflected in reports or UI
- 68714 - New Settings: While on the ‘Inventory’ settings page, typeError is thrown if you try and navigate to a different settings page, preventing you from doing so.
- 69595 - HP LaserJet CP3525dn scan error
- 70044 - Custom Groups - different count in Inventory vs. Settings
- 70833 - New scan flow/table view: invalid range cause poor user experience
- 70983 - Up/Down check doesn’t always report all down devices
- 71067 - Custom attribute error messaging when not retaining the ‘in portal?’ setting when synced from central to remote
- 71175 - Upgrade Remote Agent to use TLS1.1 and TLS1.2 (See notes below)
- 71536 - Table View: Columns misalign with headers in Firefox
- 71597 - Device Type “+” Displaying Over Search List
- 72024 - Device Scanning page does not have the warning when “Enable scheduled scanning” is disabled
- 72499 - Application Error on Cloud Services Settings page still present on version 7.5.00080(patch Dec)
- 72648 - Pivot search from table view gets stuck on loading screen
- 72800 - Table View: icon-plus (top right) on table shifting when table resized
- 72804 - Table View: column picker moves when resizing the table
- 72861 - device archiver: some admins can’t access app after successful install
- 73017 - Add “Default string” to list of bad serial numbers for Agent
- 73171 - discovery scans: additional scan settings changes
- 73200 - Handling invalid columns in the CSV Import
- 73207 - Add “Default string” to list of bad serial numbers for finder
- 73314 - correct text error on inventory scan page for “Devices could not be inventoried”
- 73447 - Unresolvable host name exclusion cause Finder to crash
- 73681 - UI should direct users to scan network hardware via SNMP, not SSH
- 73863 - Scans Stop Running on Previously Discovered Devices Due to DNS Errors
- 73965 - Agent fails to inventory because serial number starts with 0
Platform
- 61588 - app error on 403 when firewall is blocking frontend.spiceworks.com
- 67962 - Surface ‘alt_profiles’ as ‘aliases’ in the People View
- 68959 - Portal Tweaks Plugin: Needs updating
- 69272 - Mobile navigation is not supported by Rails versions before 3 - error in production logs
- 69770 - New Settings: Custom Attributes: Numbers value defaults to zero instead of rejecting characters
- 71120 - password reset tool fails with exception
- 71563 - Unitrends translation issue
- 71611 - disable editing of email address for admin accounts in people view
- 71724 - Reports - Wizard for tickets does not include the beginning date when using “Create Date” between
- 71841 - plugins (apps) not notifying user of available update in settings > manage apps
- 71890 - Settings: cannot change the ‘in portal’ status of a ‘list’ ticket attribute after the attribute is created
- 72012 - update wipes out device owners
- 72126 - Translation error on department when adding new user
- 72696 - “Developer” role now appears as option for People roles
- 72728 - Growl message field name doesn’t match actual field name in Outbox Email settings error
- 72744 - failed widget migration? blocks upgrade
- 72830 - Exported reports no longer contain email addresses
- 73034 - AD Sync w/ SSL set to ON still using Non-SSL port
- 73082 - settings > user accounts, add invitation help
- 73209 - Deleting an Inactive Person (permanently) does not put an entry in the Timeline
- 73466 - resources2.community.spiceworks.com URLs need to be HTTPS
- 74438 - Email Settings: Cannot save any email settings, instead receiving generic ‘error’ growl or no error messaging.
- 74440 - Proxy Settings: User cannot clear their proxy settings, as when they try they receive the ‘invalid hostname’ error.
- 74450 - cannot edit monitors and alerts
- 73807 - Update Desktop OpenSSL to 1.0.1r
Download the latest version here: www.spiceworks.com/download
More information on security bulletins can be found here: http://community.spiceworks.com/support/security-center/
Agent TLS support: In order to support TLS 1.1 and 1.2 in the agent, we needed to update the .Net version we use. Because of this, the new “secure” Agent is not currently integrated with the App, and is available as a separate download here: http://download.spiceworks.com/Platform-Tools/current/Spiceworks%20Agent.msi . Also note the version number is 10.0.0, so it will not be auto updated by the App integrated Agent.
1 Spice up
WOW! A bunch of updates and fixes. Thank you Spiceworks!!!
lee-y-sw
(Lee Y (Spiceworks))
4
What a list of updates… You would think our Dev Team loves our SpiceHeads or something… oh wait… they do!
1 Spice up
Question on the Agent.
So if i upgrade to this version the remote agents will not be auto updated to the new secure version?
I will have to go to each Remote computer. download the new agent and reinstall the agent again?
-Ivan
boweller
(boweller)
7
71175 - Upgrade Remote Agent to use TLS1.1 and TLS1.2
Thank you for your hard work, this is the #1 thing I’ve been waiting for!!!
billcreager2
(Bill C (Spiceworks))
8
Unfortunately, yes. This is the first step in releasing the agent from its app bindings. In the future, we will be able to upload new agent version without releasing the app. The app will be fully integrated with the new location for download, and auto update when new version are available. This also gives us the ability to have multiple version of the agent available.
So manual…for now
Great jobs guys! It looks like another mass slaying of bugs!
Awesome!
I note the Minimum specs do not include Server 2003 - we’re currently running our 7.5.00064 version on 2003 SP2 x64 - I guess this upgrade will still run on this OS? I didn’t bother to check last time I upgraded so this may have been listed previously! 
Nice! I see a couple of mine listed in there. Can’t wait to try it out, after my users leave for the day.
Thanks!
fettforce
(fettforce)
12
Working great for me so far. Thanks!!!
billcreager2
(Bill C (Spiceworks))
13
CRITICAL UPDATE - If you have downloaded and installed the newest version of the app, you are one of the majority that are not having problems with the upgrade. However, we have a number of users with an obscure problem that we didn’t see in test that cannot update. Because this number is larger then we want, we are pulling 7.5.00065 until the problem is addressed. We know the problem, and are working on a fix. As soon as we have it fixed, we will get 7.5.00065 back up.
TL;DR - There is a problem with upgrade for a number of users large then we can support in real time. We have pulled the build. If the build is up and running for you, that means you were not effected by the error, and should be good to go!
Mike400
(Mike400)
14
Would this explain the Signature alert I’m getting from both Edge and IE 11 running on Windows 10 v1511?
billcreager2
(Bill C (Spiceworks))
15
The signature alert is from a new Windows policy that came out at the beginning of the year. They are discontinuing support for SHA-1 signed certs. We currently sign with SHA-1, but are working on getting a SHA-2 signed cert.
v-s
(V_S)
16
The signature alert is a new Microsoft “feature” because Spiceworks is currently signing using SHA1, completely independent of the 7.5.00065 release.
Some more information on that can be found here - Downloading spiceworks.exe "The signature of this program is corrupt or invalid"
Typically, most people can either use a different brand browser to successfully download and install Spiceworks, or manually browse to the download location and Run as Administrator to bypass the error, also after getting the error in IE/Edge/Windows 10 some users have had the download disappear while others have not (shrugs).
For the following bug fix:
- 72499 - Application Error on Cloud Services Settings page still present on version 7.5.00080(patch Dec)
Was that supposed to say 7.5.00057 (Dec 3), 7.5.00059 (Dec 10), 7.5.00061 (Dec 30), since 7.5.00080 doesn’t seem right to me with this current release at 7.5.00065 
Does this also mean that there will be the potential to add custom installation options to this new installer or inclusion of an .ini file alongside the .msi in the same directory that will read configuration settings for the Spiceworks Server so manual entry of all of the Spiceworks Server settings and Portal Settings will not be necessary for every individual new installation of the Agent?
I assume this will also upgrade the existing install of the Agent, keeping all current settings? I’ll try it later on tonight to confirm, as I assume it will be independent of the actual 7.5.00065 release since I didn’t get it downloaded to try it before it was pulled.
las
(LAS)
17
Running fine so far and less of a lag in transitions and report generation.
It say Beta Testing on Version Check App and I am testing Everything 

UPDATE 19 Feb 2016 @ 0721 - All fixed Now 

Download link downloads 7.5.00063, not .00065. 
las
(LAS)
19
Sounds like you have a proxy cache somewhere on your internet access, try another connection.
Had this issue before with a ISP cache engine as different versions download link and filename is always Spiceworks.exe
jericom
(Jericom)
20
Hi is there any news in regards to the upgrade fix, we are one of the lucky ones that had issues upgrading.