webmasterbeta
New Member
I'm not computer specialist, but have taken several mid level computer science classes in college, I'm an internet programmer (perl, php, asp.net). Now, I just looked at a simple tutorial for SSH and it seems to make sense. -My main question is, will I be doing any crazy system configuration stuff if I sign up for an unmanaged dedicated server? -Is there like a set list of things that need to be done to a server before I can start publishing my site? -If I order MSSQL, will I have to configure it in some crazy fashion, or can I just start using it? -Is it easy to upload and install a program via SSH? Will always be running or do I control that from SSH? (.NET framework primarily) I really want to save the money and go unmanaged, but I want to be 100% sure...well, at least 95% sure that I can handle it. I knowI just asked a lot of questions, but answers to any of them would be appreciated greatly. Thanks, ChrisYou mentioned MS SQL and .NET, so I guess you are after a Windows server.Windows servers can be managed over RDC (remote desktop connection), so you could configure and install software like that. It's just like having the computer in front of you. I personally wouldn't use SSH, except perhaps as an extra way of getting into the server. Probably not as my main method of installing stuff, not for Windows anyway.I would recommend getting Plesk, as it will be much easier. Unmanaged is fine, but you might have trouble setting up nameservers (if you are going to run them on the machine) and an e-mail server. You could set up a test server at your house to see if it's something you would be able to do.From what you said about your experience, I'm sure you are capable of both, I would go for Plesk though, to make it nice and easy.man, that's everything I wanted to hear. My next question was about remote desktop, but I felt my post was getting lengthy enough. So, setting up email server, not sure about that, sure i Will have to do some serious homework on that, but I at least know where to start. I don't know where to start on figuring out nameservers. I will have 1 domain, are nameservers the address I put in my domain control panel at register.com? I.E. ns1.anotherprofile.com and ns2.anotherprofile.com. What should I search for to find more info on this? I have used plesk before, its great for .net and sql. Will it simplify setting up nameservers? thanks, this forum is unbelievably helpful. ChrisIf you go for Plesk, you won't really need to do anything. You won't need to setup an e-mail server and you won't need to setup nameservers (probably).Many hosts will hand over the Windows server with Plesk installed, and private nameservers running on your main domain.So like, whatever.com and ns1.whatever.com and ns2.whatever.comYou would "register" the ns1.whatever.com and ns2.whatever.com to point to spare IPs on your server, then change to those nameservers about 24 hours later.Not all hosts will give that setup though, so it's a good pre-sales question to ask.If you want to use Plesk and MS SQL together, from within Plesk, you will probably need the Plesk powerpack, or at least part of it (as an addon). You may aswell just go for the whole powerpack, there is some good stuff in it.If you are going to hold any kind of important data on the SQL Server then I would highly recommend that you purchase one of the packages from the many 3rd party support companies floating around here that offer initial server hardening. Let them secure your server first! Well actually, even if you are not going to hold important data like credit card numbers I would recommend it anyways. Be sure to let them know that you have SQL Server and that you want it secured as best as possible in addition to securing the rest of the server. After that, I recommend that if you can afford it, you let the 3rd party do a periodic security check for you. Good Luck!Thanks for the tip TCP Warrior, but I'm not holding any important information, and right now, my budget can barely afford the dedicated server. I went with softlayer fyi. Got a great deal, got mssql and plesk too. One more question is kinda floating around in my head though. When people say, nameservers, email servers, web servers etc. Is that all running on my dedicated server, but seperated by software or something? Are they like sections of my server? I don't really understand that.Yep, it's all running on your server, but different programs control each bit.Plesk just provides an easy way to link them all together and control them.The SoftLayer server that we got was provisioned with security in mind (they disabled exploitable services, the server polls their internal update servers looking for Windows updates on a daily basis in case you forget to do it, ETC.). The SQL server part of it though was a straight forward install that left a few security holes that needed to be secured. Other than that you should be ok. You can always block the SQL ports to the outside through the Plesk included firewall and configure all software running on the server to "speak" to SQL server through the internal IP address provided by SoftLayer. Overall, initial installation security there has been one of the better ones that we have come accross from a provider. One final recommendation: Download the Microsoft Baseline Security Analyzer (MBSA) (<!-- m --><a class="postlink" href="http://www.microsoft.com/technet/security/tools/mbsahome.mspx">http://www.microsoft.com/technet/securi ... ahome.mspx</a><!-- m -->) and run it. You might also want to run URLScan Security Tool (<!-- m --><a class="postlink" href="http://www.microsoft.com/technet/security/tools/urlscan.mspx">http://www.microsoft.com/technet/securi ... lscan.mspx</a><!-- m -->) To answer your final question... you can easily setup your nameservers through Plesk or use the ones provided by Softlayer (it will reduce server load). Cheers.<!-- m --><a class="postlink" href="http://safety.live.com/">http://safety.live.com/</a><!-- m --> Check with this too...
And as per security you need to be concern in these
-check the applicatiol pool are running under networ service
-check whether any unknown application are listening n any network port
-unknown servicesIf you are going to get windows server then i would risk and get it un managed,you can hire someone later if you stuckWell, I went unmanaged and its really not that bad, had a few issues with the .NET framework, but worked those out and now struggling a bit with connecting to my MSSQL database via my enterprise manager on this computer. I'll figure it out though. Thanks for all the input folks
whm with cpanel is also goodDarn shame that doesn't work with windows.It's in private beta testing, according to the Cpanel website. It has been for a while though. Hopefully they are just making it 100% perfect before releasing it.One of the common pitfalls of moving from managed to unmanaged hosting is in the areas such as backup and disaster recovery. While a typical managed hosting plan will have provisions for backing up and restoring your account in case of a disaster, this isn't a guarantee in the typical unmanged plan. Sometimes unmanaged dedicated hosting companies will offer some kind of backup storage that you can take advantage of, so make sure you look into this. Also, since you're managing the server yourself, you're also going to be responsible for updates and patch management. Since you're on a windows server, you can utilize windows update, which is free. It's a good option if you're managing a very small number of systems, and there are other options available for automating management of patches/updates in a larger environment. Don't neglect this. Also, the microsoft update tool will only update microsoft supported software, so if you have a control panel like plesk or other software, you'll need to keep tabs on those products to make sure that if there are any security patches that you stay updated.Well, I went unmanaged and its really not that bad, had a few issues with the .NET framework, but worked those out and now struggling a bit with connecting to my MSSQL database via my enterprise manager on this computer. I'll figure it out though.
Thanks for all the input folks
Open the SQL Server Client Network Utililty (Start -> Programs -> Microsoft SQL Server -> Client Network Utility)
Click on the "Alias" tab
Click "Add" and enter the following information:
Server Alias - Server Name
Network Library - TCP/IP
Computer Name - x.x.x.x(server IP)
Port Number - Default port nhumber is 1433
Click OK
Click OK - This will close out the Client Network Utility
Open Enterprise Manager. Right Click "Microsoft SQL Servers" and select "New SQL Server Registration" This will open a wizard. Click Next.
Select "Server Name" from the list of available servers and "Add" it. Click Next.
Choose to connect using SQL Server Authentication
Enter your assigned username and password. Keep on clicking next until the wizard is completed.
And as per security you need to be concern in these
-check the applicatiol pool are running under networ service
-check whether any unknown application are listening n any network port
-unknown servicesIf you are going to get windows server then i would risk and get it un managed,you can hire someone later if you stuckWell, I went unmanaged and its really not that bad, had a few issues with the .NET framework, but worked those out and now struggling a bit with connecting to my MSSQL database via my enterprise manager on this computer. I'll figure it out though. Thanks for all the input folks
whm with cpanel is also goodDarn shame that doesn't work with windows.It's in private beta testing, according to the Cpanel website. It has been for a while though. Hopefully they are just making it 100% perfect before releasing it.One of the common pitfalls of moving from managed to unmanaged hosting is in the areas such as backup and disaster recovery. While a typical managed hosting plan will have provisions for backing up and restoring your account in case of a disaster, this isn't a guarantee in the typical unmanged plan. Sometimes unmanaged dedicated hosting companies will offer some kind of backup storage that you can take advantage of, so make sure you look into this. Also, since you're managing the server yourself, you're also going to be responsible for updates and patch management. Since you're on a windows server, you can utilize windows update, which is free. It's a good option if you're managing a very small number of systems, and there are other options available for automating management of patches/updates in a larger environment. Don't neglect this. Also, the microsoft update tool will only update microsoft supported software, so if you have a control panel like plesk or other software, you'll need to keep tabs on those products to make sure that if there are any security patches that you stay updated.Well, I went unmanaged and its really not that bad, had a few issues with the .NET framework, but worked those out and now struggling a bit with connecting to my MSSQL database via my enterprise manager on this computer. I'll figure it out though.Thanks for all the input folks
Open the SQL Server Client Network Utililty (Start -> Programs -> Microsoft SQL Server -> Client Network Utility)
Click on the "Alias" tab
Click "Add" and enter the following information:
Server Alias - Server Name
Network Library - TCP/IP
Computer Name - x.x.x.x(server IP)
Port Number - Default port nhumber is 1433
Click OK
Click OK - This will close out the Client Network Utility
Open Enterprise Manager. Right Click "Microsoft SQL Servers" and select "New SQL Server Registration" This will open a wizard. Click Next.
Select "Server Name" from the list of available servers and "Add" it. Click Next.
Choose to connect using SQL Server Authentication
Enter your assigned username and password. Keep on clicking next until the wizard is completed.