Discussion Replies, writing homework help

Must be at least 150 words each. DO NOT JUST COMMENT ON OTHERS WRITING. Use proper APA citations.

1) Window Server 2012 Version

There are four versions of Windows Servers Datacenter, Standard, Essential, and Foundation. Deciding which versions to select will depend on the size, structure, and level of virtualization required.

Datacenter provides a highly virtualized, private cloud environment with full Windows Server functionality and unlimited virtual machines.

Standard is a step down from Datacenter, it provides the same full Windows Server functionality but it is limited to two virtual instances.

Essentials is a step down from the Standard version. It is ideal for small businesses that have as many as 25 users and up to 50 devices on the network. It does not have the full Windows Server functionality, it has a simple interface with preconfigured connectivity to cloud-based services, there are no virtualization rights.

The Foundation is for very small companies that need a Windows base Server to manage up to 15 users. The Foundation Server is a general-purpose server with basic functionality, there are no virtualization rights. Knowing which of the four categories of Windows Servers your organization belongs to is a critical factor in planning a network.

2) Server Roles in Windows

Professor Vann,

I’ve heard of a file server (which stores network users’ data files), a generic communications server (handles many common communications functions for the network, such as e-mail, fax, remote access, firewalls or Internet services), a database server (manages common databases for the network, handling all data storage, database management and requests for data), a print server (manages the printers that are connected to the network and the printing of user documents on the network printers), and an application server (shares network-enabled versions of common application software and eliminates the need for software to be installed on each workstation).

Since I have zero experience with servers, I found this website that actually adds many more types to the mix. As I understand things, a server can be configured (within reason), to manage just about anything on a network (another plus).

What are some of the different kinds of servers?

3) Some things to Consider

Class,

Let me through out a scenario for you. You are a network administrator of your company and you and your co-workers are in the planning stages of a network upgrade and you are deciding what to do. Before installing a Windows Server or any server for that matter, what are some things that you would needs to consider? A checklist of sorts, what are considerations that you need to address before proceeding?

Share from your own your experiences or what you’ve learned from the reading thus far.

4) Ch. 2

This chapter provided a good explanation of DNS. I understood it, but not quite so clearly. Now I understand the different DNS domains too. DNS servers act as translators, that’s good to know. “Any computer providing domain name services is a DNS name server.” (p. 40) – also good to know.

I actually remember WINS. Ah, DDNS and NDDNS becomes clear – knowing this explains a few issues I’ve had in the way back past, that seem to have disappeared in the current.

Iterative queries are best case answer. Recursive queries ask for either the best case answer or an error message. I think I understand the difference, especially in the two scenarios the book presents – server hasn’t got the right answer or domain name doesn’t exist. I think recursive queries are cleaner, in a sense, you know right away where you stand. Inverse queries are kind of interesting actually, makes sense though.

I get DNS zones actually. One server – multiple uses and zones of control.

Secondary zones are neat – load balancing and increased network performance – all good!

The When to Use Stub Zones provided a lot of good information – I wondered how network, particularly database, integration occurred when two companies merged. Very interesting.

I understand IPv6.

Wow, lots of different records in the list of DNS Record Types.

I love the walk-through exercises and examples. It makes what I’ve read more comprehensible, if that makes sense to anyone.

Hmm, I’ve never heard of DNS Aging and Scavenging, but it makes sense. I’d think it’d make the network vulnerable if things aren’t cleaned up.

This chapter was also a good read for me!

5) Automatic Updates

I have mixed feelings on automatic updates. There have been several times where an automatic update to a server caused issues in places I have worked. As the article below says, rebooting can be your biggest problem. Even though there was a set time when the updates happened on the server it still seemed to always disrupt the system at odd times, and/or cause the system to crash once everyone booted up their computers. On the other hand there have been issues where an update was not done at all and the servers security was compromised and a virus took every device connected to it down. If I were in charge of the update policy I think I would do critical updates automatically, but leave some of the other ones to be done at a time when not everyone is using the server at the same time to avoid the rebooting issues.

6) Supporting Activity

Before checking out a couple of articles, I’d have probably said yes – use all of the updates to Service Packs, Hot fixes and Security Patches. However, as I’m reading these articles, I’ve encountered a different point of view.

Rick Rosato recommends always updating service packs. “Service packs update systems to the most current code base. Being on the current code base is important because that’s where Microsoft focuses on fixing problems.” (para. 3). However, he goes further to say, “Individual hot fixes and security patches on the other hand should be adopted on a case-by-case, “as-needed” basis.” (para. 4.) He also lists some basic rules and generic best practices reference service packs, hot fixes, and security patches. I rather like his rules and best practices, because it isn’t just about DOING, it’s also about testing, and thinking about what you’re doing, etc. and it makes sense to me.

Fred Avolio also believes not every “update” needs to be used. He provides six steps to Patch Management.

Personally, I’d probably combine the two articles suggestions and pick out what would work for me.

7) Okay, so I typed in Installing Windows Server on a Network, and got something like 372 different courses. I chose Installing SQL Server 2012 with Gerry O’Brien. It is rated for beginners – which I am.

The neat thing about this video was he shows me how to install using the GUI or command prompt – I’m always interested in different routes that attain the same goal. He also showed me how to configure different services and network connections. I also learned how to create and connect to databases (not at all what I thought it was going to be like!).

There were two sections I particularly needed to see/hear – (well, I needed them all actually) – Testing and Backup/Restore. I know a lot more about them now, than before this video.

I’ll probably watch this again, as it was quite long and in-depth, and today was the last few minutes of viewing for me. (I’ve been watching it on and off since Tuesday). Plus, there are at least three other videos that are relatively similar that I want to watch as well. Never hurts to discover alternate ways of doing things.

8) Ch. 1

have no idea that Windows Server 2012 offer so many features and advantages, some are beneficial to the user or company while granting better security and performance. The BitLocker is a tool that most people and enterprises should have on at all times; it encrypts the hard drives of a computer. BitLocker is most useful against data thieves or unauthorized users when encrypting hard drives and removable drives; the data would be protected and keeps unwanted hands away from accessing sensitive content. The other feature that caught my interest is the Windows Deployment Services; the Administrator is allowed to install Windows OS remotely. Administrators can set up new computers by using a network-based installation when using Windows Deployment Services (Panek, 2015).