Visual Source Safe 2005 on Windows Server 2012 R2

Hi there,

We have been tasked with getting rid of all of our Windows Server 2003 servers since support for 2003 will soon end.  We currently have a Windows Server 2003 VM that hosts VSS 2005.  Instead of going to Windows Server 2008, we want to go right to Windows Server 2012 to replace this 2003 VM.  With that, can we configure VSS 2005 to work with Windows Server 2012?  If so, what is required and what additional installations do we need to do in order to get it working properly?

Thanks and please ask any questions you may have!

- Christian
Christian PalaciosSenior IT Systems AdministratorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

QlemoBatchelor, Developer and EE Topic AdvisorCommented:
It should just work. There is no real VSS server component, so all is based on file sharing, and the VSS application logic is run on the client. There is one server component (Visual SourceSafe LAN Service, SSService.exe) which runs as a service on the server, which provides faster access when using Visual Studio - and that should work the same.
I didn't try, but I see no reason that it does not work. We use VSS 2005 on W2008R2 (64bit, of course), and there are no issues.
0
pcelbaCommented:
Didn't you think about switching the source safe platform?  Subversion or Git is much better than the old VSS.
0
btanExec ConsultantCommented:
Likewise it should work out on 2012 r2 but probably you need to check the SSL based connection as 2012r2 has more stringent crypto (e.g. sslv3 and below disabled, TLS 1.2 is enabled by default) and likely your need to re-issue your ssl server cert in IIS running - https://msdn.microsoft.com/en-US/library/ms181053(v=vs.80).aspx
regardless, I do not see it as showstopper, and I believe it should be working with latest .net framework installed too. I have not tried though
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Christian PalaciosSenior IT Systems AdministratorAuthor Commented:
Hi all;

Thanks very much for the replies!  I am hoping VSS will work just fine with 2012 R2.  Does anyone have a great tutorial for how to properly install VSS?  I want to ensure I follow all of the required steps.

Thanks,
- Christian
0
btanExec ConsultantCommented:
The closest and official is likely only in MSDN on 2 core steps (though it stated 2K3)
Installing Visual SourceSafe > https://msdn.microsoft.com/en-us/library/b8e72409(v=vs.80).aspx
Adding and Configuring a Database > https://msdn.microsoft.com/en-us/library/ms181056(v=vs.80).aspx

But really i dont think that can be found and even then it is not supported per se. MS already stated the next successor is Visual Studio 2010, and no longer distributes Visual SourceSafe. MS offers Team Foundation Server Basic for smaller development teams. Understand there may be a hotfix so existing SourceSafe customers can use SourceSafe with Visual Studio 2010. The latter support Windows 2012 R2. And probably there is something to explore instead. http://alinconstantin.blogspot.sg/2013/11/using-visual-sourcesafe-2005-with.html

But do note the final version of VSS 2005, retired from mainstream support on 10 July 2012 - extended support ending on 11 July 2017...https://msdn.microsoft.com/en-us/library/aa302175.aspx
0
Christian PalaciosSenior IT Systems AdministratorAuthor Commented:
Thanks very much btan!  I'll review these documents and try to do the install on 2012 soon.

- Christian
0
Christian PalaciosSenior IT Systems AdministratorAuthor Commented:
Hi there,

Thank you, the installation appeared to have gone off very well with no issues.  I was able to create a new database and it seems to be ok, but I'll confirm that with our developers.  Is there a simple option for migrating all of the information from the old server to this new one?  If I need to start a new question, please let me know!

Thanks,
- Christian
0
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
Everything VSS knows is contained in files located in the SourceSafe base folder structure, which can be different from the VSS database location. But that is all, nothing hidden (aside from the different files keeping cached data on the VSS client side, but there is nothing you could do about that).
0
btanExec ConsultantCommented:
the upgrade steps from VSS to TFS or VS will be good reference to import data.
https://msdn.microsoft.com/en-us/library/ms253060.aspx
Specifically, you can see this
Copy and prepare your Visual SourceSafe database
--------------------------------------------------------------------------------
Copy and prepare your VSS database by following these steps:

1. Check in files.   Ideally, all files in your VSS database should be checked in. If this is not possible, as many files as possible should be checked in before you upgrade.

2. Remove access to the Visual SourceSafe projects.   You should be the only person who has access to the Visual SourceSafe projects that you are upgrading.

3. Copy the database.   Follow the instructions on this page of the Microsoft Web site: How To Back Up a Visual SourceSafe Database.

4. Upgrade the copy of your database.    If your Visual SourceSafe database is a version earlier than Visual SourceSafe 6.0, upgrade it to Visual SourceSafe 2005 by using the Visual SourceSafe DDUPD Utility.

5. Scan for and fix data integrity issues in the copy of your database.

Note: You must use the Visual SourceSafe ANALYZE utility to locate and fix data integrity issues in the database. For more information about how to use this tool, see the following pages on the Microsoft Web site: ANALYZE Utility and How to Detect and Fix Database Corruption Errors in Visual SourceSafe.
https://msdn.microsoft.com/en-us/library/ms253127.aspx#vss

And do check the migration outcome
https://msdn.microsoft.com/en-us/library/ms253170.aspx#check_results

There is a handy tool targeting the project conversion from VSS 2005 to TFS 2010 per se using VSSconvertor, if you are looking at not too many project otherwise better to follow the a/m steps if still in time ... to review ...https://msdn.microsoft.com/en-us/library/ms400685(VS.80).aspx
0
Christian PalaciosSenior IT Systems AdministratorAuthor Commented:
Great, thank you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.