tabrez
(Tabrez (Spiceworks))
1
The first build of the Spiceworks 4.0 beta is now available for you to try out. Testing and feedback from you is an integral part of every release cycle. The feedback we’ve received on the alpha builds has been extremely valuable. While there is still a lot of work left and there are still plenty of bugs we’re now opening the testing to a larger group during the beta phase.
Please read the following posts on information on how the beta program will work. Please be sure to test your favorite 3.6 features as well as the new 4.0 features!
- 4.0 Testing Guidelines
- 4.0 Testing Plan
Want to use your existing data?
Follow the instructions in the how-to on moving your installation.
Want to submit a problem report?
Follow the instructions in 4.0 Testing Guidelines
We strongly caution you against using the beta in production. If you hit a serious bug you may have to start from scratch!
** Click Here To Download 4.0 Beta I **
47 Spice ups
bdrowe2
(BDRowe2)
3
Crikey… crack on team!
Just for clarification as i know these questions will be asked:
Is it best to remove all previous Alpha versions before testing the beta?
Should we test the beta as a fresh install or with data or with both?
Ta.
Excellent! ought to try out today!
Just got this up and runnig and looking really good !!
Hi All, please remove the Alfa version and perform a clean installation without any previous data.
But then we can copy the existing db back in, correct?
Only if it is the 3.6 data that has not been migrated to 4.0.
Installing now will let you know tomorrow.
bob3813
(slylabs13)
11
Not sure if this is the proper forum for 4.0 testing reports (I didn’t call em bugs ok??)
An update on the endless loop upon saving that I reported earlier: It seems I Was editing a record that had a duplicate device with the correct Serial Number. I tried to change the originally scanned device record’s serial number to the correct one while the duplicate record still existed.
After I deleted the duplicate (that oddly had the correct serial number) I was able to edit and save the original device record’s serial number. Not sure this is a problem with 4.0 beta. This may have been the case all allong.
bob3813
(slylabs13)
12
This is the second time this has happenned. When I delete a duplicate device, I get this in the inventory window instead of the actual inventory:
Messaging.push(“missing_asset”, “Category missing. Please refresh and try again.”, {“selfRemoving”: true, “timeoutSeconds”: 10}); if($(‘summary_wrap’)){ Element.update(“item_summary”, “\n\u003Cdiv id="item_summary" class="empty empty"\u003E\n \u003Cdiv id="active_overview"\u003E\n \u003Ch4 class=""\u003EThis device has been removed\u003C/h4\u003E\n \u003Cp class="empty_sub_heading"\u003EEither the network scanner deleted this device (duplicate) or it was deleted in another Spiceworks console.\u003C/p\u003E\n \u003C/div\u003E\n\u003C/div\u003E”); } if($(‘device_1472’)){ Element.remove(“device_1472”); }
By the way, I get this when clicking on the other copy of the record. A refresh does not fix it. Only going back to the beginning of inventory and clicking on a group and drilling back down will properly display the device record.
installing on my Win7 (beta ) testbed. Look good so far. 3.6 db moved in just fine.
Lots of nice touches to the interface.
Alright, here we go, official upgrade comencing!
and I thought I was getting stuff done. beta was quick to get out the door!
ok, 4.0b is working nicely- some things are wicked slow, using ff 3.0.10 for interface. toolbar on network admins’ machine seems to run much faster.
test server is a p2.4 with only 1g ram, win2k3srvr, so it is a bit slow.
no crashes and all data is intact with the exception of the cisco ip phones we lost in inventory. not sure where they went but will keep you updated.
arno1247
(ObieOne)
19
Going to try this on our Server2008 Virtual Testserver.
I had some UAC issue’s when starting SW in the last builds.
Donwloading now…
Nice going Spiceworks the maps are working fine now - keep up the good work
