For sometime now the company I work for has been using Microsoft Virtual Server 2005 R2. It has it’s problems but as a whole it’s a very powerful application. We just recently installed Microsoft Virtual Machine Manager Beta 2, it hasn’t disappointed us. The Machine Manager is a program that you install on individual machines. It is different from Virtual PC 2007 as it is like Virtual Server it shows the VM status (running, stopped etc). It is very user friendly, unlike Virtual Server which was not straight forward and very finicky.
The main motivator for why we moved from Virtual Server 2005 to Virtual Machine Manager 2007 was for its save points feature. Yes Virtual Server has save points I do realize, but with Machine Manager you can save multiple points and label them. When you want to go back in time you can choose a past point and go back as far as you need (reminds me of restore points in Windows XP).
Another major change in Machine Manager is the way that it makes disks and stores them. No more differencing disks! I hate differencing disks. My dislike for them was spawned from my inability to re-organize disk because of there reliance to there parent disk. With a differencing disk if the parent disk becomes corrupt or is deleted or moved all of the child disks will no longer function. The new Machine Manager makes a full copy of the parent disk and then stores both the disk and the machines config file in it’s own independent folder. You can move the folder anywhere you like and it will still work like it always has.
I highly recommend Microsoft Virtual Machine Manager 2007. It is still in beta but in a whole it hasn’t been too buggy. Here is the link to download the Beta 2 Evaluation version. I don’t know how much the full version will be when it is released but you can try it out for now. Tell me what your opinion of the program is, leave me a comment.
- Kevin C -
We found our answer to our Sharepoint License issue. Stay with Sharepoint 2003 version, much cheaper! We got a quote for the Sharepoint 2007 External Connector License for about $30,000. Compare this to the 2003 license for $2,000! Since we don’t need any of the new features that MOSS offers we will happily stay with the cheap alternative. Here is a quote from a repable site about the license.
“External Connector License. An External Connector License allows an unlimited number of authenticated external users to access a server. If the number of user accounts will approach or exceed 20, the External Connector License is the most economic choice. Although there may not be 20 external users when the solution is initially implemented, consider planned usage of the technology over time before selecting the licensing type for your organization. The estimated retail price of the External Connector License is $1,999.”
Do not use the Report Server add-in for SharePoint. There is no need to use it, it has only given me a headache. All you need to do when you are running the Reporting Services Configuration Tool is to add the Reports and ReportServer Virtual Directories to the SharePoint site. I know, this seems too simple right, well it works. Please keep in mind that i am using SSL and i have not tried this otherwise. When I first started research this I came across the Reporting Services Add-In for SharePoint tutorial from here. It says to setup the Report Server on the default web site in IIS under a different port. Well this didn’t work for me so I read up and others told me to create a new sub site named something like reports. So I made reports.ourwebsite.com and SharePoint was on portal.ourwebsite.com. So now I install the add-in and I think everything is good. Then we moved our web server to a different box that was not a domain controller. Well this made problems because we had the site setup for windows authentication. While on the domain controller the website only asked for the username and password, now that IIS is on a separate box it asks for the domain\username and password. That won’t work because our customers will not know the domain name. So I moved us to Basic Authentication. The issue with this is the Report Server Add-In for SharePoint will not work with Basic Authentication. Now I am stuck having to put the Report Server back to Native mode and have our customers click a link from our portal to reports. The issue now is our customers now need to double authenticate, first to portal then to reports! Then I was recommended from a co-worker to try and just add the Report Server application pools to the SharePoint site. So I tried it even though all the documentation I’ve read seemed to completely veer away from that idea. It worked!! I added my link in the page viewer web part and it is flawless. I am able to use basic authentication and have the report integrated into my SharePoint webpage. I am kind of upset because the Microsoft website steered me on the wrong path. If you look a couple of posts down you will see a picture of the integrated Report Server in SharePoint, my new setup looks exactly the same as this. If you have any questions at all please leave me a comment and I will defiantly try and help.
- Kevin C -
I now know how Microsoft makes there money. We just upgraded to SharePoint 2007 (MOSS) and we are about to make our site public to our customers. We found that we needed to buy licences to allow our customers use SharePoint. You can reference this Microsoft page for more information about this: http://office.microsoft.com/en-us/sharepointserver/HA101655351033.aspx.
We found that it will cost about $90 for a standard use of SharePoint and about $70 extra to use the Enterprise Edition (new features from MOSS). That is about $160 per customer! There is one more option which is called an Internet Licence. This allows anyone to use your site, no separate CAL’s required. Sounds too good to be true? It costs $40,000! We have about 40 customers so I don’t think that it would be worth that. I love SharePoint but I am starting to see why open source got popular.
- Kevin C -
I’ve had a couple requests to see how the reporting service add-in for SharePoint looks like on my site. My purpose of merging the two is to allow our customers to view there current and past bug reports they had submitted to our company. I built a report to show the status of there ticket and all the notes that have been recorded on the ticket. The database that the report is quarrying is SQL and the bug tracking system we are using is TestTrack Pro. We had to convert the TestTrack Pro database to SQL from its Native database to allow for reporting. The reporting service add-in allows you to upload a report to any document library. The permissions for that report are managed by whatever permissions you define in SharePoint. Please note that the user must have sufficient permissions in the SQL database you are quarrying to allow for report viewing. The add-in also comes with a report web part which allows you to define perimeters. In my case i used the company name to allow the one report with all of our customers to be narrowed down to the specific company for report viewing on there site specific web page. If you have any questions please leave a comment.
- Kevin C -
Recent Comments