Home Forums Discussions General Discussion What to switch first

Question about what to do first.

We are migrating from P2P to server based in our office, with the excellent help of Bert, but I have yet to update to V4. Should I update my P2P first and download a fresh V4 on server and migrate data or should I put the current version on the server and then update it from there? Not sure if it makes a difference or not. Seems to me I should update first but what seems to me isn't always the right thing! IT is setting up my server next week and just would like to know if I need to be updating tomorrow or over the weekend of if after the server goes in.

Thanks,
Ron

I feel very strongly that you should get your network all set up including everything new, etc. And, then install V4 fresh on your server. While moving SQL databases is not all that hard, it can be a bit tricky, and you may as well start fresh.

I am lost... perhaps just exhausted from too many well child checks.. So you are saying get my server running and put my old AC database 3.7 or whatever on there and update on the server? The whole fresh thing is throwing me off.

OK, now I am confused, lol. I was talking about starting fresh, because that was the term used in your first question. I guess I am not being helpful as I may be misunderstanding your question. I certainly would not advise going BACK to V3.

Here is what I thought the question was. And, it's bee awhile since we talked about your client/server plans so I may be off here:

I thought you were still P2P and had not yet switched to a new server and a client/server setup (hopefully domain). Hence, the fact that your IT is setting up your server next week. So, I assumed that given your server isn't set up yet, you are still using P2P with what I would term a pseudoserver. (We really need to coin that term as it is helpful in these types of discussions)

Again, I am confused. From this statement, I would think you were still using V3.7 as you have yet to update to V4. The key for me would be is the word server in quotes above referring to your new server or a computer in your P2P that holds the AC databases?

I suppose I may be able to offer better advice after clarifying these things, but for now I would say this:

You must be using Amazing Charts daily. You must be in a P2P with some version of AC running on a pseudoserver. So, I would do nothing, I would not upgrade or change anything. I would wait for IT to set up your new server and network, and then I would download the newest version of AC there is and install the SQL databases and program on the server and go from there.

Hope this helps. Sorry for misunderstanding.

Bert you are a nightowl that is for sure. Thought I was bad

Okay..
So I have V3.7 on pseudoserver right now
Domain Server to be set up next week
Plan to install brand new V4 on server

So my concern is this. If my data that I need to move over to the domain server (by data I mean all the stuff I have on my V3.7 pseudoserver i.e chart data, imports etc..) hasn't been "upgraded" to V4 will I be able to move my data into my new fresh domain V4 program?

I just assumed that V4 would talk better with V4 as I assume that like databases are better than mixing and matching. Maybe I just don't understand the platforms and how the data is actually kept. Am I wrong? You were saying that SQLs don't like to talk?

Well, the simple answer is to leave 3.7 alone, wait for the new server and then migrate the existing data.

If you think about it, there is no difference migrating to V4 on your current "server" and then moving it to the new server than waiting.

If you migrate the data now, then you will have to move the databases and install SQL Server again on the server. It's not that you can't move them, you can. But, it just makes sense to do it once. Sure SQL can talk to SQL.

Also, I guess "main computer" on a P2P is better than pseudoserver.

Got IT!

Makes sense now that I see though the trees here.

Will get server up and going this week with IT and then start fresh and new on V4.

If I struggle there I will be sure to look you up Bert.

Thank you again for all of your help. It is truly appreciated.

Ron

I'll be around. 23/7.

Bert,

Okay. So server is up and going. How do I migrate my pseduoserver data onto V4? Do I make a copy of the database and the imports and move them into the AC folder and point it at it? How will it know where to get the imports? Do I need to delete anything. Is there anything I should know before I do this?

And finally... I would love the Bert Peds Med database for V4 and instructions on how to put it in place!

Thank you again for all your help. I have already begun to play with SBS 2003 and it is AWESOME!!! Any tips on cool things to do with SBS2003 in peds with forms etc would be much appreciated.

I am glad someone enjoys SBS2003, as I have come to loathe it and yearn for Server 2003 Standard. It is ok, but some functionality is missing and managing the standard version is what I am used to, learned in school, and feel comfortable with. Not that SBS doesn't get the job done, it certainly does.

OK. Well, first things first. @Paul, why do you loathe it. To me, the only downside is only one domain controller stipulation, but that isn't much of an issue for me. If you are like me, it is mainly because you are used to Server 2003 as stated. I eventually will move to SBS2008, but I played with it, and I hated the eye candy given it is built the way Vista is. Having the quick user switching thing drives me nuts. I definitely want logins the way it is on 2003 or 2000 for that matter.

Ron,

Send me an email at:

badams_remove AT riverviewpediatrics.org where, of course,

you remove the _remove and change that AT to @

Gotta watch the bots.

I hate that the Manage My Server screens, options, and more are different. Also, the server roles wizard in Server 2003 are much easier to work with than the other routes used in SBS. I also dislike that much of the management options only give a wizard to configure things and do not give you the option to change just one setting.

Take the Windows Firewall in SBS. I wanted to change a setting (it's been a while, I don't remember which setting) and the only way SBS would allow me to do that was to run a wizard to configure the firewall and when I wanted to change the setting back I had to run the wizard all over again, start to finish. It seems to be geared toward people that don't know their way around, which is a good thing, but there should be options, such as an advanced view if you would like to bypass the wizards you do not like. I learned on the Standard interface and to me it seems more robust, easier to use, and "makes sense" to me. Of course, when new versions come along (i.e. 2008) I will need to learn where MS hid everything (it always seems like they move things around), so I guess I should not complain too much.

I chose IT as a career and it will be an ever-changing field, and I knew that going into it. It is very fun and rewarding though and so far I really like it, even when I am complaining!

A good TechNet article on SBS and its features:

http://technet.microsoft.com/en-us/magazine/2005.11.onsite.aspx

While SBS does have some options to allow skipping some wizards, out of the box, it is the easiest server to set up. But, it is NOT for those who don't know their way around. As Jeff from Experts Exchange who has over 25 years in the business and is a Microsoft SBS MVP many times over, SBS is NOT just another OS. It is completely different.

It is, as the name suggests, built for the Small Business Environment. I can't imgine Verizon using it. In fact, they pretty much couldn't. But, the components it incorporates into it such as Sharepoint, RWW, Exchange Server, easy remote accesss, ISA firewall, and auto active directory and DNS, DHCP setup is incredible. The premium version also gives you SQL Server 2005.

Just adding on Exchange Server to SBS 2003 basically within the overall cost is worth the purchase. Certainly, even those with a fair amount of computer experience are going to have to be rather careful installing Exchange 2003 or 2007. With SBS it is already incorporated into it. And, yes with the wizard and knowing a few key IP addresses and SMTP addresses, you are in business in less than ten minutes. The downside to this is, yes, you have to go back into the wizard to get to the firewall settings or to change from SMTP to DNS with email, but that takes all of five or six clicks.

It may not be for everyone, but for those who don't want to spend a ton of money and need a really well designed server for a small business, I couldn't recommend anything better.

But, to each his own.

I agree with you and think it is a great operating system. I think when I said I loathed it so much I was using stronger words than I meant. I would say I wish there was a way to use the Server 2003 Standard interfaces, but there is - purchase that version lol! It's funny, I told everyone how much I liked Vista, after I got certified in it, because I learned the ins and outs. I thought I would never be the guy saying "I don't like that because it's different than what I am used to!" but look at me go haha!

I am trialing Win7. I think I could learn to love the Vistas if I could figure out the networking stuff. I can't figure out the bench and the public and private and everything else. Talk about your wizards and eye candy. Now, that is something that needs to be turned off. Unless, of course, you want to give me a tutorial. LOL.

Hehe, well basically all the "Network Location" selection does is set defaults on media/file sharing and "network discovery" mode. All those options are still available in the Network and Sharing Center home page with selection radio buttons. So each one of those options configures those radio button selections differently but you can go edit them to suit your needs no matter what you pick. The rest of the networking stuff is not that terrible. Ask away My biggest gripe was the exclusion on the Fax and Scan Wizard from the Home Premium version. You can still scan but it is not as simple as it was. You have to open Photo Gallery and then I think "Import-> From Scanner" or something. Don't have Vista in front of me at the moment. I wish Microsoft would stick with 2 versions of Windows. The only functionality that should be excluded for Home users should be domain joining. Having so many versions is confusing, and in my opinion a stupid move that only benefits MS and does not in any way benefit the end-user.