[Free] 2018(June) Dumps4cert Microsoft 70-646 Dumps with VCE and PDF Download 121-130

Dumps4cert.com : Latest Dumps with PDF and VCE Files
2018 May Microsoft Official New Released 70-646
100% Free Download! 100% Pass Guaranteed!

Pro: Windows Server 2008, Server Administrator

Question No: 121 – (Topic 3)

You are evaluating whether to add an additional hard disk drive to each file server and create a striped volume for the data files.

Which storage requirement is met by adding the hard disk drive and creating the striped volume?

  1. Improve data availability on the file servers.

  2. Improve the performance of the file servers.

  3. Provide additional storage on the file servers without causing downtime.

  4. Enable users to access the previous versions of all the files stored on the file servers.

Answer: B Explanation:

http://technet.microsoft.com/en-us/library/cc732422.aspx

A striped volume is a dynamic volume that stores data in stripes on two or more physical disks. Data in a striped volume is allocated alternately and evenly (in stripes) across the disks. Striped volumes offer the best performance of all the volumes that are available in Windows, but they do not provide fault tolerance. If a disk in a striped volume fails, the data in the entire volume is lost.

You can create striped volumes only on dynamic disks. Striped volumes cannot be extended. You can create a striped volume onto a maximum of 32 dynamic disks.

Question No: 122 – (Topic 3)

You need to recommend a solution that enables User1 to perform the required actions on

the HyperV server. What should you include in the recommendation?

  1. Active Directory delegation

  2. Authorization Manager role assignment

  3. local security groups on the Hyper-V server

  4. local security groups on the VMs

Answer: B Explanation:

http://technet.microsoft.com/en-us/library/dd283030(v=ws.10).aspx

You use Authorization Manager to provide role-based access control for Hyper-V. For instructions on implementing role-based access control.

Authorization Manager is comprised of the following:

Authorization Manager snap-in (AzMan.msc). You can use the Microsoft Management Console (MMC) snapin to select operations, group them into tasks, and then authorize roles to perform specific tasks. You also use it to manage tasks, operations, user roles, and permissions. To use the snap-in, you must first create an authorization store or open an existing store. For more information, see http://go.microsoft.com/fwlink/?

LinkId=134086.

Authorization Manager API. The API provides a simplified development model in which to manage flexible groups and business rules and store authorization policies. For more information, see Role-based Access

Control (http://go.microsoft.com/fwlink/?LinkId=134079).

Authorization Manager requires a data store for the policy that correlates roles, users, and access rights. This is called an authorization store. In Hyper-V, this data store can be maintained in an Active Directory database or in an XML file on the local server running the Hyper-V role. You can edit the store through the Authorization Manager snap-in or through the Authorization Manager API, which are available to scripting languages such as VBScript.

If an Active Directory database is used for the authorization store, Active Directory Domain Services (AD DS) must be at the Windows Server 2003 functional level.

The XML store does not support delegation of applications, stores, or scopes because access to the XML file is controlled by the discretionary access control list (DACL) on the file, which grants or restricts access to the entire contents of the file. (For more information about Authorization Manager delegation, see http://go.microsoft.com/fwlink/?LinkId=134075). Because of this, if an XML file is used for the authorization store, it is important that it is backed up regularly. The NTFS file system does not support applications issuing a sequence of separate write operations as a single

logical write to a file when multiple applications write to the same file.

This means an Authorization Manager policy file (XML file) could be edited simultaneously by two administrative applications and could become corrupted. The Hyper-V VSS writer will back up the authorization store with the server running the Hyper-V role. http://technet.microsoft.com/en-us/library/cc725995(WS.10).aspx

A role assignment is a virtual container for application groups whose members are authorized for the role. A role assignment is based on a single role definition, and a single role definition can be the basis of many role assignments.

The most common procedure that administrators carry out is the assignment of application groups, or Windows users and groups, to a role. For step-by-step instructions, see Assign a Windows User or Group to a Role or

Assign an Application Group to a Role.

Question No: 123 – (Topic 3)

You need to recommend a solution for managing App1. The solution must require the minimum amount of administrative effort.

What should you include in the recommendation?

  1. Group Policy Administrative Templates

  2. Group Policy Preferences

  3. Group Policy Software Settings

  4. Windows Remote Management (WinRM)

Answer: B Explanation:

Get total application control with Windows Group Policy Preferences (GPP).

With GPPs added to Group Policy, you’ll find that your level of customized control increases substantially. The graphical interface used in creating a GPP makes the process of managing an application’s configuration, mapping a drive, or adding a new registry key far easier as well as going far beyond what was possible using traditional Group Policy.

Note:

Group Policy preferences, new for the Windows Server 2008 operating system, include more than 20 new Group Policy extensions that expand the range of configurable settings within a Group Policy object (GPO). These new extensions are included in the Group Policy Management Editor window of the Group Policy Management Console (GPMC), under the new Preferences item. Examples of the new Group Policy preference extensions include folder options, mapped drives, printers, scheduled tasks, services, and Start menu settings.

Group Policy preferences provide better targeting, through item-level targeting and action modes. Additionally, rich user interfaces and standards-based XML configurations provide you with more power and flexibility over managed computers when you administer GPOs.

Question No: 124 – (Topic 3)

You need to recommend a Windows update strategy for the new branch office. What should you recommend doing in the new branch office?

  1. Deploy WSUS in replica mode. Configure updates to be stored on the new WSUS server.

  2. Deploy WSUS in autonomous mode. Configure updates to be stored on the new WSUS server.

  3. Deploy WSUS in replica mode. Configure the WSUS clients to retrieve updates from Microsoft Update.

  4. Deploy WSUS in autonomous mode. Configure the WSUS clients to retrieve updates from Microsoft Update.

Answer: C Explanation:

New office has a 2MMbps link to the internet and only a 512Kbps link to HQ. so configuring WSUS to update from MS Update will meet the requirement to minimize WAN Link utalization. Making the WSUS server a replica will meet the requirement to minimize the administrative effort to approve updates as all updates would be approved in HQ and this approval would be replicated out to the branch offices.

http://technet.microsoft.com/en-us/library/dd939820(WS.10).aspx Replica mode (centralized administration)

In replica mode, an upstream WSUS server shares updates, approval status, and computer groups with downstream servers. Downstream replica servers inherit update approvals and are not administered separately from the upstream WSUS server.

The following image shows how you might deploy replica WSUS servers in a branch office environment.

Dumps4Cert 2018 PDF and VCE

Question No: 125 – (Topic 3)

You need to identify which operating system must be installed on the HyperV server in the new branch office. Which operating system should you identify?

  1. a Server Core installation of Windows Server 2008 R2 Enterprise

  2. a Server Core installation of Windows Server 2008 R2 Standard

  3. Windows Server 2008 R2 Enterprise

  4. Windows Server 2008 R2 Standard

Answer: A Explanation:

Hyper-V has specific requirements. Hyper-V requires an x64-based processor, hardware- assisted virtualization, and hardware data execution prevention (DEP). Hyper-V is available in x64-based versions of Windows Server 2008-specifically, the x64-based versions of Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows Server 2008 Datacenter technical requirements include minimizing attach surface, Server Core

achieves this. so should you use Enterprise or Standard as Hyper V can be implemented on both x64 versions? http://www.directionsonmicrosoft.com/sample/DOMIS/update/2008/02feb/0208ws2plp_ch.h tm

  1. Windows Server 2008 Standard, Enterprise, and Datacenter are also offered in quot;without Hyper-Vquot; editions that do not include the hypervisor technology.

  2. When customers exercise the maximum number of OS instances permitted by the server license, the physical OS instance may not be used to run any workload beyond hosting the virtual machines.

  3. A single package contains both 32-bit and 64-bit versions. The server license grants the customer the option to use either the 32-bit version or the 64-bit version of the software.

  4. Supports hot addition of memory, but not hot replacement of memory, nor hot add or replacement of processors.

  5. Use of Windows Server 2008#39;s new Terminal Services Gateway capability is limited to 250 connections.

  6. Includes restrictions limiting scalability.

  7. Volume licensing customers typically receive additional discounts of 10% to 30%. 8 Client Access Licenses (CALs) retail for US$40 apiece but are offered to volume

customers for as much as 50% off. External Connectors are available only via volume licensing programs. Pricing for an External Connector starts at approximately US$1,800 in the least-discounted programs

Under the planned changes it states that each branch will have one DC, a DirectAccess Server a File Server and a Web Server and that all branches will be virtualised. therefore you will be running 4 VMs Windows server 2008 Enterprise allows the running of 4 VMS on one license

So the answer is A becase Server core reduces the surface attack area and virtualization on Enterprise server will meet the VM and licensing requirements

Topic 4, Baldwin Museum of Science Scenario:

COMPANY OVERVIEW

The Baldwin Museum of Science is an internationally renowned museum of science history.

Physical Location

The museum has a main office and a branch office named Branch1. The main office has 5,000 users. Branch1 has 1,000 users.

The main office connects to Branch1 by using a WAN link. The WAN link is highly saturated.

The museum has a sales department. All of the users in the sales department have client computers that run Windows XP Service Pack 3 (SP3).

EXISTING ENVIRONMENT

Active Directory Environment

The network contains one Active Directory forest. The forest contains two domains named baldwinmuseumofscience.com and ad.baldwinmuseumofscience.com.

All user accounts and computer accounts for all employees are in the ad.baldwinmuseumofscience.com domain. The organizational unit (OU) structure for ad.baldwinmuseumofscience.com is shown in the exhibit. (Click the Case Study Exhibits button.)

Dumps4Cert 2018 PDF and VCE

Network Infrastructure

The network contains the following servers and Applications:

  • Application servers that run either Windows Server 2003 Service Pack 2 (SP2), Windows Server 2008 SP2, or Windows Server 2008 R2.

  • A custom Application named App1 that runs on all of the Application servers. App1 writes events to the Application log.

  • A line-of-business Application named App2 that requires Internet Explorer 6. All of the users in the sales department run App2.

  • File servers that run Windows Server 2008 R2. The main office has the following:

  • A two-node failover cluster that runs Windows Server 2008 R2 and has the Hyper-V role installed and a Clustered Shared Volume. The failover cluster hosts four virtual machines (VM) that run Windows Server 2008 R2. The VMs are stored on the Clustered Shared Volume. Each VM runs Microsoft SQL Server 2008.

  • A server named Server1 that hosts two shared folders named Sharel and Share2. Sharel hosts 50,000 research documents that are shared by multiple users. Share2 hosts documents that are created by users in the sales department.

    Administration Model

    All users in Branch 1 are members of global groups and universal groups. The groups are located in an OU named Groups in the ad.baldwinmuseumofscience.com domain.

    REQUIREMENTS

    Planned Changes

    The Baldwin Museum of Science plans to implement a new branch office named Branch2. Branch2 wi and will be configured as a separate Active Directory site.

    Branch2 will be configured to meet the following requirements:

  • Minimize the cost of deploying new servers.

  • Contain only client computers that run Windows 7.

  • Connect to the main office by using a saturated WAN link.

  • Contain only servers that run Windows Server 2008 R2. The servers will be configured as either file servers or Web servers. The file shares on the file servers must be available if a single file server fails.

    In Branch2, if a single domain controller or a WAN link fails, users in the branch must be able to:

  • Change their passwords.

  • Log on to their client computers.

    Technical Requirements

    The Baldwin Museum of Science must meet the following technical requirements:

  • Hardware and software costs must be minimized whenever possible.

  • All VMs must be backed up twice a day.

  • All VM backups must include the VM configuration information.

  • Events generated by App1 must be stored in a central location.

  • An administrator must be notified by e-mail when App1 generates an error.

  • The number of permissions assigned to help desk technicians must be minimized.

  • The help desk technicians must be able to reset the passwords and modify the membership of all users in Branch1.

  • If a user overwrites another user#39;s research document, the user must be able to recover a previous version of the document.

  • When users in the sales department work remotely, they must be able to access the files in Share1 in the minimum amount of time.

  • Security

    The Baldwin Museum of Science must meet the following security requirements:

    ->All scripts that run on production servers must be signed.

    ->Managers in Branch1 must be allowed to access the Internet at all times.

    ->Web site administrators must not be required to log on interactively to Web servers.

    ->Users in Branch1 must only be allowed to access the Internet between 12:00 and 13:00.

    ->Users and managers must be prevented from downloading executable files from the Internet.

    ->Administration of the corporate Web sites must support all bulk changes and scheduled content updates.

    Question No: 126 – (Topic 4)

    You need to recommend a highavailability solution for the file servers in Branch2 that supports the museum#39;s planned changes. What should you include in the recommendation?

    1. a standalone Distributed File System (DFS) namespace and DFS Replication

    2. a domain-based Distributed File System (DFS) namespace and DFS Replication

    3. Failover Clustering and Clustered Shared Volumes

    4. Network Load Balancing (NLB) and Storage Manager

    Answer: B Explanation:

    Distributed File System (DFS)

    DFS is a method of both simplifying your organization’s shared folder structure and providing data redundancy through replication. DFS lets you collect shared folders located on different servers into one or more logically structured namespaces. Rather than having to remember which server hosts a specific shared folder, they can access the DFS namespace and find all shared folders.

    You can replicate a DFS namespace and folders within a site and across WAN links. A user connecting to files within the shared folder structures contained in the DFS namespace will connect automatically to shared folders in the same Active Directory Directory Services (AD DS) site (when available) rather than across a WAN. You can have several DFS Namespace servers in a site and spread over several sites, so if one server goes down a user can still access files within the shared folder structure. The architecture of DFS ensures that a change to a file on a DFS share is replicated quickly and efficiently to all other replicas of that DFS share.

    Creating a DFS Namespace

    You can create a namespace when you install the DFS Management role service, as shown in Figure 10-2, or create it later.

    You can add additional namespaces by right-clicking DFS Namespaces in the DFS Management console and selecting New Namespace. You can create namespaces on a member server or domain controller running Windows Server 2008. However, you cannot create more than one namespace on a server running Windows Server 2008 Standard edition. You can create multiple namespaces on servers running Windows Server 2008 Enterprise and Datacenter editions.

    A namespace is a virtual view of shared folders in an organization, and it has a path to a namespace similar to a Universal Naming Convention (UNC) path to a shared folder. You can create two types of namespaces:

    Domain-Based Namespaces

    A domain namespace uses a domain as its namespace root, such as

    \\adatum.com\MyNameSpace. A domainbased namespace can be hosted on multiple namespace servers to increase its availability, and its metadata is stored in AD DS. Domain-based namespaces can be created on one or more member servers or domain controllers in the same domain, and metadata for a domain-based namespace is stored by AD DS. Each server must contain an NTFS volume to host the namespace. Multiple namespace servers increase the availability of the namespace. A domain-based namespace cannot be a clustered resource in a failover cluster. However, you can locate the namespace on a server that is also a node in a failover cluster provided that you configure the namespace to use only local resources on that server.

    Standalone Namespaces

    A stand-alone namespace uses a namespace server as its namespace root, such as

    \\ServerA\MyNameSpace.

    A stand-alone namespace is hosted on only one server. You would choose a stand-alone namespace if your organization does not use AD DS, if you needed to create a single namespace with more than 5,000 DFS folders but your organization did not support Windows Server 2008 mode, or if you wanted to use a failover cluster to increase availability.

    Question No: 127 – (Topic 4)

    You need to recommend a domain controller deployment strategy for Branch2 that meets the museum#39;s technical requirements.

    What should you recommend for Branch2?

    1. Deploy two writable domain controllers in ad.baldwinmuseumofscience. Configure both domain controllers as global catalog servers.

    2. Deploy two read only domain controllers (RODCs) in ad.baldwin museum of science. Configure both RODCs as global catalog servers.

    3. Deploy one writable domain controller in baldwinmuseumofscience.com and one writable domain controller in ad.baldwinmuseumofscience. Enable universal group membership caching.

    4. Deploy one read only domain controller (RODC) in baldwinmuseumofscience.com and one writable domain controller in ad.baldwinmuseumofscience. Enable universal group membership caching.

    Answer: A Explanation:

    http://technet.microsoft.com/en-us/library/dd735489(WS.10).aspx

    Read-only domain controllers (RODCs) do not introduce any significant new considerations for determining whether to make a branch domain controller a global catalog server. Global catalog placement generally requires planning unless you have a single-domain forest. In a single-domain forest, you can configure all domain controllers as global catalog servers without causing any additional replication or an increase in disk size or CPU usage.

    However, only domain controllers that are designated as global catalog servers can respond to global catalog queries on the global catalog Lightweight Directory Access

    Protocol (LDAP) port 3268. Designating all domain controllers as global catalog servers eliminates server or network capacity planning concerns about which domain controllers can respond to global catalog queries by applications or other domain controllers.

    In a multiple-domain forest, deciding whether a domain controller should be a global catalog server takes extra planning. As a general rule, it is best to make branch-office domain controllers (including branch-office RODCs) be global catalog servers so that authentication-and, generally, any global catalog query-can be performed by using just the RODC. This comes, however, at the price of replicating the partial attribute set for objects from every domain in the forest to the branch office, which may be expensive in terms of network and disk usage if some domains have large amounts of users, computers, or groups with a high rate of updates.

    If you determine that you cannot make the branch-office domain controller a global catalog server, you should enable universal group caching in that site. With universal group membership enabled, a domain controller must connect to a global catalog server across a wide area network (WAN) link only for initial logons in the site.

    Thereafter, universal group membership can be checked from a local cache.

    Question No: 128 – (Topic 4)

    You need to recommend a solution for controlling access to the Internet. The solution must meet the museum#39;s security policy.

    What should you include in the recommendation?

    1. File Server Resource Manager (FSRM) file screens and Group Policy objects (GPOs)

    2. Microsoft Forefront Threat Management Gateway (TMG) 2010

    3. Microsoft Forefront Unified Access Gateway (UAG) 2010

    4. Windows Firewall with Advanced Security and Group Policy objects (GPOs)

    Answer: B Explanation:

    http://www.microsoft.com/download/en/details.aspx?displaylang=enamp;id=14238

    Forefront Threat Management Gateway 2010 allows employees to safely and productively use the Internet without worrying about malware and other threats.

    It provides multiple protection capabilities including URL filtering*, antimalware inspection*, intrusion prevention, application- and network-layer firewall, and HTTP/HTTPS inspection –

    that are integrated into a unified, easy to manage gateway, reducing the cost and complexity of Web security.

    http://www.isaserver.org/tutorials/Creating-Web-Access-Policy-Forefront-Threat- Management-Gateway-TMGBeta-1-Part1.html

    Question No: 129 – (Topic 4)

    You need to recommend a management solution for the corporate Web sites that meets the museum#39;s security policy. What should you include in the recommendation?

    1. Internet Information Services (IIS) Manager

    2. Remote Desktop Services (RDS)

    3. Remote Server Administration Tools (RSAT)

    4. Windows PowerShell 2.0

    Answer: D Explanation:

    RSAT isnt right because that will give them access to other tools they do not need. the admins are not required login in so that takes care of RDS because that means they MUST log on interactively, that leaves IIS and Powershell.

    PowerShell meets the requirements of the security policy, IIs wont

    Question No: 130 – (Topic 4)

    You need to recommend a solution for the research documents that meets the museum#39;s technical requirements. What should you recommend?

    1. On all client computers, enable shadow copies and configure the Previous Versions client settings.

    2. On Server1, enable shadow copies. On all client computers, configure the Previous Versions client settings.

    3. Deploy Microsoft SharePoint Foundation 2010, and then migrate Share1 to a new document library. Modify the blocked file types.

    4. Deploy Microsoft SharePoint Foundation 2010, and then migrate Share1 to a new document library. Enable versioning for the library.

    Answer: B Explanation:

    Possible answers are B amp; D, the consensus is B as it doesn’t require the investment in other technology and one of your requirements is to minimize costs

    Sharepoint versioning Versioning is the method by which successive iterations of a document are numbered and saved.

    The default versioning control for a document library depends on the site collection template. However, you can configure versioning control for a document library depending on your particular requirements. Each document library can have a different versioning control that best suits the kind of documents in the library. SharePoint Foundation 2010 has three versioning options:

    No versioning Specifies that no previous versions of documents are saved. When versioning is not being used, previous versions of documents are not retrievable, and document history is also not retained because comments that accompany each iteration of a document are not saved. Use this option on document libraries that contain unimportant content or content that will never change.

    Create major versions Specifies that numbered versions of documents are be retained by using a simple versioning scheme (such as 1, 2, 3). To control the effect on storage space, you can specify how many previous versions to keep, counting back from the current version.

    In major versioning, every time a new version of a document is saved, all users who have permissions to the document library will be able to view the content. Use this option when you do not want to differentiate between draft versions of documents and published versions. For example, in a document library that is used by a workgroup in an organization, major versioning is a good choice if everyone on the team must be able to view all iterations of each document.

    Create major and minor (draft) versions Specifies that numbered versions of documents are retained by using a major and minor versioning scheme (such as 1.0, 1.1, 1.2, 2.0, 2.1). Versions ending in .0 are major versions and versions ending with non-zero extensions are minor versions. Previous major and minor versions of documents are saved together with current versions. To control the effect on storage space, you can specify how many previous major versions to keep, counting back from the current version. You can also specify how many major versions being kept should include their respective minor versions. For example, if you specify that minor versions should be kept for two major versions and the current major version is 4.0, then all minor versions starting at 3.1 will be kept.

    In major and minor versioning, any user who has read permissions can view major versions of documents. You can specify which users can also view minor versions. Typically, we recommend that you grant permissions to view and work with minor versions to the users who can edit items, and restrict users who have read permissions to viewing only major

    versions.

    Use major and minor versioning when you want to differentiate between published content that can be viewed by an audience and draft content that is not yet ready for publication.

    For example, on a human resources Web site that describes organizational benefits, use major and minor versioning to restrict employees#39; access to benefits descriptions while the descriptions are being revised.

    Configuring Volume Shadow Copy on Windows Server 2008 http://www.techotopia.com/index.php/Configuring_Volume_Shadow_Copy_on_Windows_S erver_2008

    Once shadow copy has been configured for volumes on the server, the next step is to learn how to access the previous version of files from client systems. This is achieved using a feature of Windows Server 2008 and Windows Vista called Previous Versions.

    To access previous versions of a file on a client, navigate to the shared folder (or subfolder of a shared folder) or network drive using Start -gt; Network. Once the desired network drive or shared folder is visible, right click on it and select Restore Previous Versions (or just Previous Versions on Windows Vista). Once selected, the Properties dialog box will appear with the Previous Versions tab pre-selected as illustrated in the following figure:

    There are a number of issues that need to be considered when implementing shadow copy for shared folders. First and foremost the shared folders which are to be shadowed need to be identified. Secondly, a location for the shadow to be stored must be allocated. This can reside either on the same volume as the shared folders, or on a completely different volume or disk drive. Even before any data is shadowed, the shadow copy system requires 300MB of available space. The total amount of space required will depend on the size of the shared folder which is to be shadowed and the frequency and extent to which the files are likely to change (since shadow copy will only take new snapshots of files which have changed since the last snapshot). Finally, the time and frequency of the volume snapshots needs to be defined. By default, Shadow Copy performs a snapshot twice a day at 7:00am and 12:00pm.

    Once the Shadow Copy system has been configured the shadow copy client needs to be set up on the systems of any users that are likely to need to be able to restore files in shared folders.

    Using Computer Management to Enable and Configure Volume Shadow Copies

    Shadow Copy is enabled on a per volume basis. Once configured on a volume, all shared

    folders residing on that volume will automatically be shadowed. Shadow Copy can be configured either graphically using the Computer Management tool or via the command prompt. Command-line configuration of Shadow Copy will be covered in a later section of this chapter. This section will focus on Computer Management configuration.

    The first step is to launch the Computer Management configuration tool (Start -gt; All Programs -gt; Administrative Tools -gt; Computer Management). Once invoked, select Storage -gt; Disk Management from the tree in the left panel to display the disk and volume information for the local system. In the graphical view, right click on a volume and select on Properties to launch the properties dialog. In the properties dialog, select the Shadow Copy tab to display the Shadow Copy properties as illustrated in the following figure:

    Dumps4Cert 2018 PDF and VCE

    T

    The Select a volume section of the properties dialog lists the volumes present on the local system. Select the volume in this list for which Shadow Copy is to be enabled. With the volume selected click on the Settings button to display the following Shadow Copy Settings dialog box:

    Dumps4Cert 2018 PDF and VCE

    n

    the Located on this volume specify the volume on which the shadow copies are to be stored. This can be either the current volume or a different volume on the system. The Details button displays free and total disk space information for the currently specified volume. Once a suitable volume for the shadow copies has been selected the maximum size to be made available for the shadow copies may be defined. This can either be set to Maximum size which will use all available space on the specified volume, or capped to a specific size (keeping in mind that a minimum of 300MB is required for the shadow storage volume even before any snapshots are taken). Shadow Copy uses a differential approach to backing up files in that only files that have changed since the last snapshot are copied. For certain files, Shadow Copy also only copies the part of the file that has changed, rather than the entire file. As such, it is not necessary to reserve 64 times the size of the volume to be copied since only parts of the volume will be copied with each snapshot.

    Schedule the shadow copy snapshots by clicking on the Schedule… button. By default, Windows configures two snapshots each day (at 7:00am and 12:00pm respectively). To remove a currently defined snapshot, select it from the drop down list and click on Delete. To modify a run, select it from the drop down list, modify the settings in the lower section of the dialog and click on OK.

    To specify additional schedules, click on the New button and specify the days and time of the snapshot. Note that snapshots can also be configured to occur at user logon, system startup and even when the system is idle.

    In fact, Windows Server 2008 provides considerable flexibility in terms of scheduling shadow copies. It is important to keep in mind, however, that there are disadvantages to running a shadow copy too frequently.

    Firstly, shadow copies are resource intensive tasks, especially on large volumes where many files are subject to frequent changes. Repeated snapshots during periods when the server is heavily utilized may well degrade overall system performance. Secondly, it is important to keep in mind that Shadow Copy retains the last 64 versions of a file.

    Therefore, if a snapshot is run every hour, the oldest restore point available to a user will be approximately two and half days in the past. If, on the other hand, snapshots are taken twice a day, the user will have the luxury of restoring a file from a point as much as 32 days ago. It is important, therefore, to strike a balance between longevity and frequency.

    The following screenshot illustrates the Shadow Copy scheduling dialog:

    Dumps4Cert 2018 PDF and VCE

    Once the schedules have been configured, click on OK to dismiss the scheduling dialog. Click OK once again in the Settings dialog to return to the Shadow Copy properties panel. At this point, the volume for which a schedule has been defined will have a small clock image superimposed over the volume icon and will indicate that 0 bytes of shadow copy storage have been used. The next step is to enable shadow copies on the volume by selecting the volume from the list and clicking on the Enable button. The volume in the list will update to display the date and time of the next scheduled copy and provide a summary of the current level of storage space used for the shadow copies.

    To initiate a manual shadow copy now, or at any other time, simply select the volume to be copied from the list in the Shadow Copy properties panel and click on the Create Now button.

    Restoring Shadow Copy Snapshots from Clients

    Once shadow copy has been configured for volumes on the server, the next step is to learn how to access the previous version of files from client systems. This is achieved using a feature of Windows Server 2008 and Windows Vista called Previous Versions.

    To access previous versions of a file on a client, navigate to the shared folder (or subfolder of a shared folder) or network drive using Start -gt; Network. Once the desired network drive or shared folder is visible, right click on it and select Restore Previous Versions (or just Previous Versions on Windows Vista). Once selected, the Properties dialog box will appear with the Previous Versions tab pre-selected as illustrated in the following figure:

    Dumps4Cert 2018 PDF and VCE

    As shown in the previous figure, the Previous Versions property page lists the previous versions of the shared folder that are available for restoration. A number of options are available for each shadow copy snapshot listed in the properties dialog. Open will open the

    folder in Windows Explorer so that individual files and sub-folders can be viewed and copied. The Copy… button allows the snapshot of the folder and its contents to be copied to a different location. Finally, Restore… restores the folder and files to its state at the time of the currently selected shadow copy snapshot. As outlined in the warning dialog, this action cannot be undone once performed.

    100% Dumps4cert Free Download!
    Download Free Demo:70-646 Demo PDF
    100% Dumps4cert Pass Guaranteed!
    70-646 Dumps

    Dumps4cert ExamCollection Testking
    Lowest Price Guarantee Yes No No
    Up-to-Dated Yes No No
    Real Questions Yes No No
    Explanation Yes No No
    PDF VCE Yes No No
    Free VCE Simulator Yes No No
    Instant Download Yes No No

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.