You have been hired by Shiv LLC as an Information Technology consultant to devel
ID: 3663448 • Letter: Y
Question
You have been hired by Shiv LLC as an Information Technology consultant to develop a technology proposal. Shiv LLC manufactures and distributes solar panel for the consumer market. Your job is to submit a proposal that meets their criteria. Current Implementation/Concerns: • The company will have 3 locations (Los Angeles, Dallas, and Houston) but are planning to grow rapidly due to high demand in solar panels. Main staff will be at Dallas and Houston offices. • Data security is priority since patent and trademarks are at stake. • Los Angeles sales personnel will need secure remote access to Houston office. • The WAN connectivity is in place and it is not an issue. There is ample bandwidth in place. • Feel free to make other assumptions but they need to be noted in the paper. Topics to Cover: Your document should cover the content presented in the course. The outline below contains recommended points to cover. You are free to add other related information. Describe the technical and business reasons for each choice, citing other resources as appropriate. The Windows Server 2012 operating system should be used for all aspects of the solution. The topics include: Active Directory: • What forest/domain model should Shiv LLC implement? What is the domain name? • Where should the domain controllers be place? Should RODC be part of the consideration? • FSMO Roles placement • Plan for AD backup and recovery Group Policy: • Is Group Policy needed? • What settings might be considered via Group Policy? DNS: • What namespace should Shiv LLC implement? • What types of zones needed? File Services: • How will the shares be secured? • Will quotas be used? FSRM be configured? • Will DFS be implemented? Remote Services: • What technology will be implemented to provide secure remote access for users? • Who should have remote access? WSUS: • How will the servers and clients be updated? • How will new servers be deployed?
Explanation / Answer
Expired and unexpired deadlines
If the client contacts the server after the update deadline has passed, it will try to install the update as soon as possible. WSUS administrators can set update deadlines to a date in the past in order to have clients install the update immediately.
If the deadline has not passed, the client will download the update and install it the next time an install occurs. For example, if the client downloads an update with a deadline of 6:00 A.M., and the scheduled installation time is 3:00 A.M., the update will be installed at 3:00 A.M. Likewise, if a user starts an install before a (downloaded) update's deadline, the update will be installed.
Deadlines and updates that require restarts
Updates that have deadlines and require restarts will cause a forced restart at the time of the deadline, no matter when the update was actually installed. For example, if an update with a 6:00 A.M. deadline was downloaded and installed at 3:00 A.M., but the computer was not restarted at that time, it will be restarted at 6:00 A.M.
Moreover, if the computer is pending restart (because another update requiring a restart was installed, but the computer was not restarted), and an update with a deadline is installed, the computer will be restarted. The following is an example of client behavior with an unexpired deadline:
The following is an example of client behavior with an expired deadline:
WSUS updates and deadlines
A WSUS update (an update that is required in order for WSUS to continue functioning correctly) has installation priority over other kinds of update. If an update with a deadline is blocked by a WSUS update, the deadline will apply to the WSUS update, as in the following sequence of events:
If the deadline of a blocked update has expired, the WSUS update that is blocking it will be installed immediately.
Understanding Dynamic Update
Applies To: Windows Server 2008, Windows Server 2008 R2
Domain Name System (DNS) client computers can use dynamic update to register and dynamically update their resource records with a DNS server whenever changes occur. This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use Dynamic Host Configuration Protocol (DHCP) to obtain an IP address.
The DNS Client service and the DNS Server service support the use of dynamic updates, as described in Request for Comments (RFC) 2136, "Dynamic Updates in the Domain Name System." The DNS Server service allows dynamic update to be enabled or disabled on a per-zone basis at each server that is configured to load either a standard primary or directory-integrated zone. By default, the DNS Client service dynamically updates host (A) resource records in DNS when the service is configured for TCP/IP.
How client and server computers update their DNS names
By default, computers that are statically configured for TCP/IP attempt to dynamically register host (A) resource records and pointer (PTR) resource records for IP addresses that are configured and used by their installed network connections. By default, all computers register records based on their fully qualified domain name (FQDN).
The primary full computer name, an FQDN, is based on the primary DNS suffix of a computer,appended to its computer name.
Additional considerations:
Dynamic updates can be sent for any of the following reasons or events:
When one of the previous events triggers a dynamic update, the DNS Client service (not the DHCP Client service) sends updates. This is designed so that if a change to the IP address information occurs, corresponding updates in DNS are performed to synchronize name-to-address mappings for the computer. The DNS Client service performs this function for all network connections on the system, including connections that are not configured to use DHCP.
Example: How dynamic update works
Typically, dynamic updates are requested when either a DNS name or an IP address changes on the computer. For example, supposethat a client named oldhost is first configured in System properties with the following names.
Computer name
oldhost
DNS domain name of computer
tailspintoys.com
Full computer name
oldhost.tailspintoys.com
In this example, no connection-specific DNS domain names are configured for the computer. Later, the computer is renamed from oldhost to newhost, which results in the following name changes on the system.
Computer name
newhost
DNS domain name of computer
tailspintoys.com
Full computer name
newhost.tailspintoys.com
After you apply the name change in System properties, you are prompted to restart the computer. When the computer restarts Windows, the DNS Client service performs the following sequence to update DNS:
Dynamic updates are sent or refreshed periodically. By default, computers send a refresh once every seven days. If the update results in no changes to zone data, the zone remains at its current version and no changes are written. Updates result in actual zone changes or increased zone transfer only if names or addresses actually change.
When the DNS Client service registers host (A) and pointer (PTR) resource records for a computer, it uses a default caching Time to Live (TTL) of 15 minutes for host records. This determines how long other DNS servers and clients cache a computer's records when the records are included in a query response.
Secure dynamic update
DNS update security is available only for zones that are integrated into AD DS. When you directory-integrate a zone, access control list (ACL) editing features are available in DNS Manager so that you can add or remove users or groups from the ACL for a specified zone or resource record.
By default, dynamic update security for DNS servers and clients can be handled as follows:
Computer name
oldhost
DNS domain name of computer
tailspintoys.com
Full computer name
oldhost.tailspintoys.com
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.