Jump to content


Search the Community

Showing results for tags 'System Center 2012'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 56 results

  1. I am looking for a resource to tell me what the different options for state messages mean for System Center Configuration Manager 2012. I saw a tech doc for 2007, but it doesn't go as high as topic type 2001. For example I have seen a lot of State Message with "topic type = 2001, state id = 3, and error code = 0x00000000" I found something that said definition of Topic type 2001 was the following: SCEP SU2 Deployment state: Installation status (installed, failed, Restart required, Unmanaged, Pending, not supported) and error details My questions. Is above explanation correct and does the list follow the numbers? meaning..... 2001 state id=1 means installed 2001 state id=2 means failed 2001 state id=3 means restart 2001 state id=4 means unmanaged....etc. Thanks for your help.
  2. I work in an environment where there are different IT depts that handle different locations and what I would like to do is be able to limit the OSD task sequences that are visible at a location. Is that even possible?
  3. I am having nothing but trouble with my SCCM 2012. I am running Server 2012 Standard, SQL server 2012 and SCCM with Endpoint Protection SP1. The install looks like it goes well but when i start to try and use client push i start to get all types errors. Under site status i have a critical staus for the Management point. And under component status my SMS_MP_CONTROL_MANAGER and SMS_NOTIFICATION_SERVER components have a critical stauts as well. I already have tried reinstalling a total of three time. If any one had any help or insight into my issues please help!!! I have attatched my log files.
  4. Customize the Organization LogoYou can customize the organization logo of the App Controller console. To customize the organization logoNavigate to the website root of the App Controller installation directory. By default, this is %PROGRAMFILES%\Microsoft System Center 2012\App Controller\wwwroot. Create a backup of the default organization logos by renaming the files as follows: a. Rename SC2012_WebHeaderLeft_AC.png to SC2012_WebHeaderLeft_AC.png.old b. Rename SC2012_WebHeaderRight_AC.png to SC2012_WebHeaderRight_AC.png.old Copy your logo into the wwwroot folder. The images must meet the following requirements: Location: Top Left Image Name: SC2012_WebHeaderLeft_AC.png Size: 287x44 Location: Top Right Image Name: SC2012_WebHeaderRight_AC.png Size: 108-16 The logos that you can change appear at the top of the App Controller site. SC2012_WebHeaderLeft_AC.png SC2012_WebHeaderRight_AC.png
  5. Connect App Controller to A VMM Management ServerOn the App Controller server, open a browser and navigate to the app controller site (in this lab example my site URL is https://SCSM.SC.LAB). Click on the ‘Connect a Virtual Machine Manager server and…’ link. In the Connect dialog box, enter a name for this connection. This name is displayed in the Name column of Clouds page. Add an optional description in the Description text box. In the Server name text box, enter the fully qualified domain name (FQDN) of the VMM management server. In the Port field, enter a port number that matches the port used by the VMM management server (default: 8100). Check Automatically import SSL certificates if you plan to copy files and templates to and from VMM cloud libraries. NOTE: SSL certificates must be imported to the App Controller server in order to copy files or templates to and from VMM cloud libraries. In order for the import to succeed, users need to be part of all of the following roles: the local administrator of the App Controller server, local administrator of the VMM server, and VMM administrator. Click OK to create the connection. You may then be asked to select which VMM user role to use from the new VMM server connection for the current session. NOTE: You may encounter the following error. See the following TechNet thread: http://social.technet.microsoft.com/Forums/en-US/047ba638-81de-4870-a3fd-6f2390633685/app-controller-2012-sp1-rtm-connection-failed-with-virtual-machine-manager-2012-sp1-rtm. Excerpt: “If System Center App Controller and the VMM Server are installed on separate servers, single sign-on does not work when App Controller is used. So, in UR1 for SC 2012 issue was fixed, but in SP1 present again. Solution is to disable SSO and use Basic Authentication or install App Controller on VMM server, but be aware 443 port VMM used for BITS.”
  6. Enable Single Sign-On How to Enable Single Sign-On for App ControllerBy default, App Controller is enabled to prompt users to sign in by entering their Active Directory user name and password. The following procedures describe how to configure App Controller to use the user’s current Windows credentials to automatically sign on. To verify or change the authentication methodOpen IIS manager on the App Controller server. Select the App Controller website. Expand the website and select the /api node. Click Authentication. Enable Windows Integrated Authentication. Disable Basic Authentication. To turn on constrained delegationLog on using an account that has OU Administrator privileges in Active Directory Domain Services. Ensure that this account is also granted the SeEnableDelegationPrivilege user right (for example, a domain administrator could run the command ntrights -u domain\user +r SeEnableDelegationPrivilege on a domain controller, where domain/user represent the domain and account name for the account). In Active Directory Users and Computers, right-click the App Controller system and click Properties. Click the Delegation tab. Select the Trust this computer for delegation to specified services only option. Select the Use any authentication protocol option. Click Add and then do one of the following: a. If the VMM management server is running under the Local System account, enter the name of the VMM management server and select HOST, and then click OK. b. If the VMM management server is running under a domain account, enter the name of domain account and select SCVMM, and then click OK. Restart the App Controller management server.
  7. Install System Center App ControllerWe are now finally ready to install SCAC. Install PrerequisitesTo start, before we will actually be able to install SCAC, we have to install a few prerequisites. § .NET Framework 3.5 SP1 § .NET Framework 4.0 § IIS (Web Server role) o Static Content o Default Document o Directory Browsing o HTTP Errors o ASP.NET o .NET Extensibility o ISAPI Extensions o ISAPI Filters o HTTP Logging o Request Monitor o Tracing o Basic Authentication o Windows Authentication o Request Filtering o Static Content Compression o IIS Management Console § VMM Console Install SCACStart by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as mu_system_center_2012_app_controller_with_sp1_x64_dvd_1345042.iso). Start by running the Setup.exe. On the splash screen click the Install link. On the Product Registration page, enter your Product Key and press Next. Read and accept the License Terms, then press Next. The Prerequisite checker will run and indicate if there is any missing components. You will note that you can still press Install, as the setup will install any missing prerequisites for you. The installation will install any missing pieces. On the Configuration page, you can change the Installation Path if you need to, then press Next. Next you need to configure the Services that App Controller will use. You can choose either a Network Service Account or a Domain Account. Make an appropriate selection and then click Next. Next you have to configure the website by specifying an IP Address, along with a Certificate. Since I don’t have a Certificate Authority in my lab, I chose ‘Generate self-signed certificate’. Then click Next. Now setup the configuration required for the database connection. In this lab example since I have SQL Server installed on the same server as App Controller, I am using LocalHost. Fill in your appropriate SQL Server information, and then click Next. Now you can decide if you want to join the CEIP program or not, and then click Next. On the Summary page, review the selections made and then click Install. Once the setup is complete, click Finish. You can opt to check the ‘Start the App Controller website when Setup closes’ if you want to launch the site right away. Else, you will have to enter the appropriate URL in your browser. When you launch the website, you will be presented with a login screen. This is because the site is not setup for single sign-on (we will cover this in a Configuration Guide later). Enter your credentials and click Sign In. Once you sign in, you will see the App Controller site, similar as follows.
  8. Install SQL Server At this point, since we will be installing SQL Server on the same server that we will be installing App Controller, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET Framework Installation To install the specific version of .NET that we require (version 3.5 in this case), start by launching the Server Manager, and selecting Manager > Add Roles and Features. On the Add Roles and Features Wizard, read the information on the Before You Begin screen, and then click Next. On the Installation Type screen, select ‘Role-based or feature-based installation’, and click Next. On the Server Selection screen, since we are installing SQL on the same server as Orchestrator, ensure that it is selected, and then click Next. On the Server Roles screen, we are not installing a Role, but rather a Feature, so just click Next. On the Features screen, select .NET Framework 3.5 Features, and click Next. Since in Windows Server 2012 the .NET Framework 4.x is the main framework, the OS installation does not contain the source files for this installation. Therefore, you will need to click on the ‘Specify an alternate source path’ link at the bottom of the dialog. You will need to provide the path to where the source files are. This is found within the installation media of Windows Server 2012. If you insert a DVD or mount an ISO, specify the path to the SxS folder (i.e. D:\Sources\SxS), and then press OK. Click Install, and once it has completed, click Close. SQL Installation Start by either extracting or mounting the SQL Server ISO, and run the setup.exe. In this example, we are installing SQL Server 2012 SP1. On the main installation screen, click on the Installation link on the left pane. From the Installation screen, click the ‘New SQL Server stand-along installation or add features to an existing installation’ link. This is initiate the installation. First, the Setup Support Rules will check for any issues. As long as there isn’t any ‘Failed’ issues, click OK to continue with the installation. Next, enter your product key or select the evaluation copy to install, and press Next. Accept the License Terms and choose if you will send usage data to Microsoft, then press Next. If you have an Internet connection, the installer will check if there are any applicable updates to the installation, and will download the updates to use during the install. Click Next. The Setup will perform another Setup Support Rules check. As long as there are no Failures, you can click Next. Next is the Setup Role. For our needs, we will choose ‘SQL Server Feature Installation’, then press Next. For the Feature Selection, select the following, and then press Next. § Database Engine Services § Management Tools – Basic and Complete (for running queries and configuring SQL services) The Installation Rules will run to determine if anything will block the SQL installation. If there are no Failures, click Next. Next we will configure the instance. You can choose either to use a Default instance, or a Named instance. In this example, I will use a named instance, so as to not get this installation of SQL mixed up with any other I will have in my lab. Make your applicable choice, and click Next. The setup will check and confirm there is enough space on the drive for the installation. If everything is reported as OK, click Next. You next have to configure the server, which includes the Service Accounts and Collation. In Production, it is best practice to have a separate account for each of the services. In our lab, we will leave everything at defaults, with the exception of changing the ‘SQL Server Agent’ startup type from ‘Manual’ to ‘Automatic’. After you have completed this, don’t click Next, but rather click on the Collation tab. On the Collation tab, you will need to click the Customize button to be able to change it appropriately. On the Customize dialog, select ‘SQL collation, used for backwards compatibility’. Within the list, find ‘SQL_Latin1_General_CP1_CI_AS’ and select it, then click OK. You will be back on the Server Configuration dialog, click Next. On the Database Engine Configuration screen, leave the Authentication Mode at ‘Windows authentication mode’. What do have to change is to add SQL Server Administrators. Click the Add button. On the next dialog, you will need to add either the user(s) or security group(s) you want to have administrator access to SQL. At a bare minimum, add the current user account, so that you can log into SQL Server. Add the user(s)/security group(s), and click OK. You will be back on the Database Engine Configuration screen, and your accounts will now be present. In my example, I have an Active Directory Security Group I specifically created for SQL Administrators. Then click Next. You can choose to send Error Reporting information to Microsoft. Make your choice, and click Next. The setup will now re-check the configuration rules, based on the selections and information that has been supplied. If it passes, click Next. Review the information on the Ready To Install screen, and then click Install. Note: during the installation, you may encounter the following error message. This is due to not having the .NET Framework 3.5 installed prior to attempting to install SQL Server. If you encounter this, cancel the SQL server installation, and install the .NET Framework 3.5 (which is an available feature within Roles and Features). You may have to wait a while for the Installation Progress to complete. On the Complete screen, click Close. Congratulations, you now have SQL Server installed and are finally ready to install System Center App Controller (SCAC).
  9. Install Active Directory Domain Services Now that we have the VMs created, and the OS installed on both, we need to first install/setup Active Directory (AD). When you log into a new installation of Server 2012, Server Manager will auto launch. From Server Manager, click on Manage, and choose ‘Add Roles and Features’. On the Add Roles and Features Wizard, read the information on the Before You Begin dialog, and then click Next. On the Installation Type screen, select ‘Role-based on feature-based installation’ and then click Next. On the ‘Server Selection’ screen, since we are installed Active Directory on this local system, ensure that it is selected, and click Next. Side note: Windows Server 2012 has a new feature that allows you to remotely install Roles and Features on other systems. On the Server Roles screen, select ‘Active Directory Domain Services’. When you select ‘Active Directory Domain Services’, immediately you will be presented with the following dialog. Click Add Features. On the Features screen, accept what has already been selected by default, and click Next. On the AD DS screen, read the information presented, and click Next. On the Confirmation screen, check the ‘Restart the destination server automatically if required’ checkbox, and then click Install. Note: You are not required to check the ‘restart’ checkbox, however, you’re going to have to restart the system anyways after the installation, so you might as well let the system do it for you. Note: When you check off the ‘Restart the destination server automatically if required’ checkbox, you will immediately be prompted with the following dialog. Click Yes. On the Results screen, click Close. After the system restarts, and Server Manager launches, you will have to promote the server as a domain controller. This is because Active Directory has been installed, but that process does not automatically promote the server. Click on the ‘Promote this server to a domain controller’ link. On the Deployment Configuration screen, select ‘Add a new forest’ since this is the first domain controller in our lab. Then enter a root domain name, and click Next. In my example I am using “SC.LAB” for System Center Lab (since I will be installing all other System Center products in my lab eventually). For the Domain Controller Options, select the appropriate Forest functional level, and Domain functional level. This is more applicable if you already have an existing domain and are adding a new domain controller. But since this is the first domain controller in our new domain, then we’ll use the highest level, that of Windows Server 2012. Also, don’t forget to create the Directory Service Restore Mode password. Then press Next. On the DNS Options screen, you can ignore this warning message and click Next. On the Additional Options screen, click Next. On the Paths screen, normally you would change the location for the database, log files, and SYSVOL, but since we are just in a lab environment, we’ll leave it at the defaults and click Next. On the Review Options scree, review what you have entered/selected, and click Next. The Prerequisites Check screen will check and confirm that everything passes before promoting the system as a domain controller. You will notice in my screenshot, that I have 1 warning because I didn’t set a static IP for the server yet. After installation completes, the system will automatically restart. You will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. When you login, you will then see in the Server Manager, that AD DS is now listed, along with DNS. Now all that you need to do is assign a static IP to your domain controller. To do this, in Server Manager, select Local Server from the panel on the left. From there, click on the Ethernet link labelled ‘IPv4 address assigned by DHCP, IPv6 enabled’. This will cause the Networks Connections explorer to open. From here, right click on the Ethernet network that is displayed. This is in fact the network connection that we configured when we first created the VM. On the Ethernet Properties dialog, select ‘Internet Protocol Version 4 (TCP/IPv4)’ and click the Properties button. Within the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, enter a static IP, gateway, and DNS that is applicable to your network. Once all the items have been entered, click OK. You will also have to click Close on the Ethernet Properties dialog as well. Congratulations, you now have a domain setup in your lab environment. Add Systems to Your Domain Now that you have your domain setup, you need to add your other VM (the one that we will use for DPM) to the domain before being able to install DPM. Log into the system you want to add to the domain. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, select the Domain option for ‘Member of’, and enter the domain name you want to join and press OK. After pressing OK, you are immediately presented with a Windows Security dialog, in which you need to enter the credentials of an account that has Domain Admin rights. Enter the credentials and click OK. Once the system is successfully joined to the domain, you will receive the following Welcome message. Press OK. After you press OK to the Welcome message, you will receive a second prompt, indicating that you need to restart the system for the changes to take effect. You will be back on the System Properties dialog. Press Close. When you press Close, you will receive yet another prompt about restarting the system. You can choose to Restart Now or Restart Later, but you won’t be able to install App Controller without the VM being added to the domain. After the system restarts, you will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. Now we have our Active Directory server setup and ready, and the VM we will be installing App Controller on is joined to the domain.
  10. Install the Operating System Now that we have created the VMs for our lab, we can install the Operating System (OS). Start by connecting to one of the VMs, either by double clicking on the VM in Hyper-V Manager, right click the VM and choose Connect, or click on Connect from the Action pane/menu. When you have the VM connection up, and an ISO mounted, power the VM on. On the Windows Setup screen, select the Language, Time/Currency Format, and Keyboard Method appropriate, and click Next. All you have to do now is click Install Now. Next you have to choose the Operating System and version you want to install. In our lab example, I will choose Windows Server 2012 Standard (Server with a GUI). Make your selection and then click Next. You will have to accept the license terms, and then click Next. For the Installation Type, since we don’t already have an OS installed, we will choose the ‘Custom: Install Windows only (advanced)’ option. Now select the hard drive that you want to install the OS to. Since we only created one hard drive when setting up the VM, we only have one to choose from. Select it, and click Next. Now all you have to do is wait for the installation to finish. Once the installation is complete, you will be prompted to enter a password for the local administrator account. This is different from a domain-based local administrator account. Enter a password and click Finish. After some final quick configuration, you will then be presented with the login screen. Now repeat these steps for the other VMs in the lab. NOTE: After you install an OS, you will need to rename the computer within the OS. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, enter the name you want to call the computer. In my lab, I called the Active Directory computer “AD”, and the App Controller computer “SCAC”. Press OK after entering the name. You will encounter the following prompt. Click OK. Then click Close on the System Properties dialog. You can choose to either Restart Now or Restart Later, but the name change will not take effect until you do so.
  11. Introduction: I use Hyper-V in my LAB and that's what all these virtual machines will be running on. In my lab, I have Windows Server 2012 Datacenter installed as the server OS on the host machine. All other virtual machines will be running Windows Server 2012 Standard edition, with the graphical user interface (GUI). My hardware consists of the following: § Intel Xeon E5-2620 § Asus P90X79 WS § 64 GB G.Skill Ripjaws Z Series § 2 x 256 GB / 1 x 512 GB Samsung 840 Pro Series SSD § 1 x 150 GB HDD, and 1 x 250 GB HDD High Level Plan Here is a high level of what we are going to complete in this initial part of the series. 1. Create the Lab Environment 2. Install the Operating System 3. Install Active Directory Domain Services 4. Install SQL Server 5. Install System Center App Controller So now let’s start with the first part, system requirements and creating the lab environment. System Requirements Note: The following page on TechNet describes the requirements for deploying AppController. Server§ OS: Windows Server 2008 R2 or Windows Server 2012 § CPU: Dual-Processor, Dual-Core, 2.8 GHz (x64) or greater § RAM: 1 gigabyte (GB) of RAM minimum, 4 GB or more recommended § HDD: 1 gigabyte (GB) of available hard disk space § Software: o Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012: § Database Engine Service § SQL_Latin1_General_CP1_CI_AS collation o Microsoft .NET Framework 4.0 o Web Server (IIS): § Static Content § Default Document § Directory Browsing § HTTP Errors § ASP.NET § .NET Extensibility § ISAPI Extensions § ISAPI Filters § HTTP Logging § Request Monitor § Tracing § Basic Authentication § Windows Authentication § Request Filtering § Static Content Compression § IIS Management Console o VMM Console Create the Lab Environment: Hyper-V Configuration As mentioned, my environment uses Hyper-V. So, we’re going to start by configuring Hyper-V for our needs, and creating the Virtual Machines (VMs) required for our lab. The first thing we need to do is setup a Virtual Switch for the VMs to connect through. Launch Server Manager, click on Tools, and select Hyper-V Manager. When Hyper-V loads, it will have nothing in it. Even if we were to create a VM, it wouldn’t have a network connection to use. So we’ll start with creating a Virtual Switch. As you can from my screenshot, I have 2 LAN ports on my host. One of them has a connection to my home network and the Internet. In the Hyper-V Manager, click the Virtual Switch Manager from the Actions pane. Now, click on the Create Virtual Switch button. From here, you now need to configure the virtual switch that your VMs will use. Give it a name to clearly identify it (in my case I called it ‘External Network’), and choose the connection type. For more information about virtual networks, see the following TechNet article: http://technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx. Here is an excerpt from the article: External virtual networks. Use this type when you want to provide virtual machines with access to a physical network to communicate with externally located servers and clients. This type of virtual network also allows virtual machines on the same virtualization server to communicate with each other. This type of network may also be available for use by the management operating system, depending on how you configure the networking. (The management operating system runs the Hyper-V role.) For more information, see “A closer look at external virtual networks” later in this topic. Internal virtual networks. Use this type when you want to allow communication between virtual machines on the same virtualization server and between virtual machines and the management operating system. This type of virtual network is commonly used to build a test environment in which you need to connect to the virtual machines from the management operating system. An internal virtual network is not bound to a physical network adapter. As a result, an internal virtual network is isolated from all external network traffic. Private virtual networks. Use this type when you want to allow communication only between virtual machines on the same virtualization server. A private virtual network is not bound to a physical network adapter. A private virtual network is isolated from all external network traffic on the virtualization server, as well any network traffic between the management operating system and the external network. This type of network is useful when you need to create an isolated networking environment, such as an isolated test domain. For our demonstration, we are going to use an External Network so that the VMs can communicate with the Host system. Make all the appropriate selections and so forth, and then press OK. You may encounter the following warning message. This is because we are remotely connecting to the Host machine using the same network connection that we are about to setup as a Virtual Switch (hence selecting the ‘Allow management operating system to share this network adapter’ checkbox). Press ‘Yes’ to the dialog. Now that we have the virtual switch setup, we can start creating VMs for our lab. Create the Virtual Machines Let’s now create the VM’s we will need for the lab, specifically one for Active Directory, and another for App Controller (since we are install all roles within the same server). In Hyper-V Manager, from the Actions pane, click on New and choose Virtual Machine. On the New Virtual Machine wizard beginning screen, click read the information presented and then click Next. Enter a name for the VM. Note that this is NOT the name the VM will have within the Operating System (unless you name it the same), but rather, used as an identifier in Hyper-V Manager. After you have entered a name, click Next. Now assign the amount of memory you want your VM to have, and then press Next. This is the screen where you connect your VM to the network that we created, then press Next. This is the screen where you configure how large a hard drive the VM will have. Make the appropriate customizations and click Next. For the Installation Options, choose if you will install an OS later, or if you want to use an ISO, then click Next. On the Summary screen, review your selections and entries, and click Finish. Once the VM is created, it will appear in the Hyper-V Manager. If you want to configure further settings, like the number of CPUs and mounting an OS ISO, right click on the VM and choose Settings or click on Settings from the Actions pane. Repeat these steps for each VM you need to create, in our case one for Active Directory and another for App Controller. Here are the settings I have used for each of the VM’s: Active Directory: § Virtual Machine Name: AD § Memory: 2048 MB o NOTE: Active Directory doesn’t need 2 GB of RAM, it will run fine with 512 MB. I just increased the RAM so that the OS would install/respond faster during setup. § CPUs: 2 § OS: Windows Server 2012 SCAC: § Virtual Machine Name: SCAC § Memory: 4096 MB § CPUs: 2 § OS: Windows Server 2012
  12. Protection GroupsIn order for DPM to protect our data, we need to have the DPM Protection Agent installed. But that’s not enough. We also need to add the system to a Protection Group. That’s what we will document here. Start by launching the DPM console, and navigating to the Protection area. On the toolbar at the top of the console, click on New. On the Welcome page, review the information presented, and then click Next. On the Protection Group Type page, choose whether you are protecting Servers or Clients. For our lab example, we will choose Servers, and then click Next. On the Select Group Members page, expand the Server(s) and select what you want to protect. When you select what you want to protect, it will automatically be added to the Selected Members list, then click Next. On the Data Protection Method, give the Protection Group a name (like PROD Active Directory Servers), and choose either short-term and/or long-term protection, then click Next. For this lab example, since I don’t have a Tape Library to simulate long-term backups, I will only use short-term. On the Short-Term Goals page, you can set a retention range, sync frequency, recovery points, and backups; then click Next. On the Disk Allocation page, review the information modifying it in required, then click Next. On the Replica Creation Method page, choose either Automatic or Manual, and then click Next. On the Consistency Check Options page, it is recommended to perform consistency checks on the data. You may also opt-in to performing daily checks. Then click Next. On the Summary page, review the selections made, and then click Create Group. Depending on how many systems and the amount of data, it may take a little while to complete. Once the task is complete, the Results will show Success. Click Close. Back in the DPM console, you will now see the system you added, along with the items being protected.
  13. Install Protection AgentNow that we have DPM installed, it doesn’t protect our environment if there are no Agents installed. Start by launching the DPM console and navigating to the Management space. Next click on the Agents link. In the toolbar, click Install. On the Agent Installation Wizard, Agent Deployment Method page, there are 2 options to choose from. Since we are starting new, we will choose ‘Install Agents’. Then click Next. On the Select Computers page, select the computer(s) that you want to protect from the list on the left, and press ‘Add’. Once you have added all the computers you want to install the Agent on, click Next. Next you need to provide credentials for the account to install the Agent. Then click Next. On the Restart Method page, chose whether to restart the computer after installing the agent or not. Your decision may be based on the location/use of the system (i.e. Production vs. Development). Make your choice and click Next. On the Summary page, click Install. Once the installation is complete, the Installation page will show ‘Success’. Click Close. Back in the DPM console, you will see your newly added system with an Agent Status of ‘OK’. You will notice that the Agents section (on the left) that it shows 0 Protected, 1 Unprotected Agents. We have to create Protection Groups.
  14. Configure System Center Data Protection Manager – Configure End User Recovery Configure Active DirectoryIn reference to this TechNet article, by configuring Active Directory Domain Services to support end-user recovery. Start by launching the DPM console, and click on Management. In the toolbar at the top of the screen, click on Options. On the Options dialog, on the ‘End-User Recovery’ tab, click on the ‘Configure Active Directory’ button. On the Configure Active Directory dialog, supply credentials with permissions to update Active Directory. Then press OK. You will encounter the following message, click Yes. You will also encounter this other message, press OK. NOTE: You may encounter the following error message. Press OK. We have to perform a workaround to accomplish this. Extend Active Directory SchemaSince there is an issue with using the Configure Active Directory option, we have to perform a workaround. The reason is the way the security of Windows Server is configured. The workaround is to use the DPMADSchemaExtension tool, located in C:\Program Files\Microsoft System Center 2012\DPM\DPM\End User Recovery\. In order to run this tool logon to a domain controller map to the directory above and run DPMADSchemaExtension.exe. Log onto a domain controller, and copy the DPMADSchemaExtension.exe tool from the DPM server to the domain controller. Right-click on the EXE and choose ‘Run as Administrator’. On the following prompt, click Yes. Enter Data Protection Manager Computer Name, note this is not the FQDN name of the server, but just the server name. Then press OK. Enter Data Protection Manager Server domain name, note this will be the FQDN domain name so if your domain is yourdomain.local enter yourdomain.local. Then press OK. Enter Protected Computer Domain Name. This field can be left blank if the DPM server is in the same domain as the Domain Controller that owns the Schema master role. On this information dialog, press OK. You may encounter the following prompt, especially if you are attempting this on Windows Server 2012. You will have to close this dialog, install .NET Framework 3.5 and then re-run the DPMADSchemaExtension.exe tool on the Domain Controller. After having successfully installed .NET Framework 3.5, and re-running the DPMADSchemaExtension.exe tool, when it completes you should encounter this message. Press OK. Log back into your DPM server, and open the Options window. On the End-User Recovery tab, you will notice that the ‘Configure Active Directory’ button is now disabled, and the ‘Enable End-User Recovery’ checkbox is available. Ensure that this checkbox is selected, and press OK. You will encounter the following information message, press OK.
  15. Configure System Center Data Protection Manager – Add Disks Adding a Physical Disk to a Hyper-V Virtual Machine NOTE: Some of these steps will need to be completed on the physical Hyper-V host, and others will be completed in the DPM VM after you have installed the Operating System. In order for DPM to be able to use a hard drive for backups, it needs to be attached to the DPM system only. For example, even though we have virtual machine running DPM, we cannot use .VDHX hard drives. That means we need a physical disk from the Hyper-V host to be made available to the DPM VM. It is important to note that if you have a hard drive that is present and visible to the physical Hyper-V host, you won’t be able to connect it to the VM. Here’s a screenshot of the Disk Management console on my physical host machine. You will note that there are 2 disks that are Offline. I am going to use one of these for my DPM backup storage. In looking at my DPM VM settings, I have added another IDE Hard Drive. I have set the drive to Physical Hard Disk, and as you can see in the screenshot, I can choose one of the 2 drives that were Offline in my physical host. If any of those drivers were Online on the host, although Unallocated, they would not appear in the selection. Now on my DPM VM system in File Explorer, you can see that although we added that physical disk in the Hyper-V settings, it is not appearing in the system. We need to launch the Disk Management console. When it opens, you will see the physical disk that we attached, but notice that it is also ‘Offline’. We need to right-click on the Offline disk, and choose ‘Online’. You will notice that even though the disk is now Online, that the space is still Unallocated. This is fine as DPM will prepare the disk when we add it to the tool. Add Disks to DPM Now that we have a physical disk available to the VM, we need to add disk(s) to the DPM tool. Start by launching the DPM console. Within the console, click on Management. In the Management space, click on Disks. In the toolbar at the top, click on Add. In the Add Disks to Storage Pool dialog, locate the disk(s) you want to include, and click the Add button. When you have added all the disks you want, click OK. You may encounter the following Warning message. Click Yes. Once the disk(s) have been added, they will appear in the DPM console, ready for use.
  16. Install DPM Self Service RecoveryThe Self-Service Recovery Tool (SSRT) for System Center 2012 – Data Protection Manager (DPM) enables end users to recover SQL Server databases that are backed up by the DPM server, without any intervention from the DPM administrator. Start by mounting/extracting the ISO (just like when we installed DPM). On the splash screen, click the DPM Self Service Recovery link. Read and agree to the License Terms, and then click OK. On the DPM Self Service Recovery Tool page, click Install. The installation will be very quick. Then click Finish. That’s it! The Self Service Recovery Tool has now been installed. We will need to do some configuration within DPM to make it work, but that will be covered in a Configuration Guide.
  17. Install System Center Data Protection ManagerWe are now finally ready to install DPM. Install PrerequisitesTo start, before we will actually be able to install SCDPM, we have to install a few prerequisites. § .NET Framework 3.5 SP1 Install SCDPMStart by either extracting the DVD contents, or mounting the ISO (the TechNet ISO is currently labelled as mu_system_center_2012_data_protection_manager_with_sp1_x64_dvd_1359086.iso). Start by running the Setup.exe. On the splash screen click the Data Protection manager link. Read and agree to the License Terms, and then click OK. Data Protection Manager will prepare to install. On the Welcome page, click Next. On the Prerequisites Check page, choose what type of database DPM will use; either a dedicated instance, or an existing instance. Basically, will it use a local SQL install or a remote install. Since we are doing this in a lab, I will choose the ‘Use the dedicated instance of SQL Server’ option, to install a local instance on the DPM server. Make your choice and then click Check and Install. The Prerequisites Check will check the system for any issues preventing installation. If there are issue, you will need to resolve them prior to being able to continue with the installation. Once you are able to continue, click Next. On the Product Registration page, enter a User Name, Company, and a Product Key, then click Next. Unfortunately, I am not aware of any way to install an evaluation version of the application, although all other System Center products provide this option. On the Installation Settings page, you can specify the location to install DPM, along with the Database files. Make any changes required and then click Next. On the Security Settings page, provide a password for the DPM SQL service account, then click Next. On the Microsoft Update Opt-In page, choose if you want to include the product in Microsoft Updates, then click Next. On the Customer Experience Improvement Program page, you can choose if you want to join the CEIP program or not. Make your choice and then click Next. On the Summary of Settings page, review the selections/choices made, and then click Install. The installation will begin, and will take a while since DPM will also install SQL Server for you automatically. Once the installation is complete, click Close. Once the Data Protection Manager Setup wizard is closed, it will automatically launch Windows Update and check for updates.
  18. Installing SQL Server first is not required, as DPM will automatically install SQL Server for you as part of the application installation process. Since I install SQL on the local System Center server for each product, my example will allow DPM to install SQL on its own. If anyone is looking for instructions on installing SQL Server, please see my personal blog: http://adinermie.wordpress.com/lab-environment/system-center-2012-sp1-in-a-lab-installation-part-d-install-sql-server/
  19. Install Active Directory Domain Services Now that we have the VMs created, and the OS installed on both, we need to first install/setup Active Directory (AD). When you log into a new installation of Server 2012, Server Manager will auto launch. From Server Manager, click on Manage, and choose ‘Add Roles and Features’. On the Add Roles and Features Wizard, read the information on the Before You Begin dialog, and then click Next. On the Installation Type screen, select ‘Role-based on feature-based installation’ and then click Next. On the ‘Server Selection’ screen, since we are installed Active Directory on this local system, ensure that it is selected, and click Next. Side note: Windows Server 2012 has a new feature that allows you to remotely install Roles and Features on other systems. On the Server Roles screen, select ‘Active Directory Domain Services’. When you select ‘Active Directory Domain Services’, immediately you will be presented with the following dialog. Click Add Features. On the Features screen, accept what has already been selected by default, and click Next. On the AD DS screen, read the information presented, and click Next. On the Confirmation screen, check the ‘Restart the destination server automatically if required’ checkbox, and then click Install. Note: You are not required to check the ‘restart’ checkbox, however, you’re going to have to restart the system anyways after the installation, so you might as well let the system do it for you. Note: When you check off the ‘Restart the destination server automatically if required’ checkbox, you will immediately be prompted with the following dialog. Click Yes. On the Results screen, click Close. After the system restarts, and Server Manager launches, you will have to promote the server as a domain controller. This is because Active Directory has been installed, but that process does not automatically promote the server. Click on the ‘Promote this server to a domain controller’ link. On the Deployment Configuration screen, select ‘Add a new forest’ since this is the first domain controller in our lab. Then enter a root domain name, and click Next. In my example I am using “SC.LAB” for System Center Lab (since I will be installing all other System Center products in my lab eventually). For the Domain Controller Options, select the appropriate Forest functional level, and Domain functional level. This is more applicable if you already have an existing domain and are adding a new domain controller. But since this is the first domain controller in our new domain, then we’ll use the highest level, that of Windows Server 2012. Also, don’t forget to create the Directory Service Restore Mode password. Then press Next. On the DNS Options screen, you can ignore this warning message and click Next. On the Additional Options screen, click Next. On the Paths screen, normally you would change the location for the database, log files, and SYSVOL, but since we are just in a lab environment, we’ll leave it at the defaults and click Next. On the Review Options scree, review what you have entered/selected, and click Next. The Prerequisites Check screen will check and confirm that everything passes before promoting the system as a domain controller. You will notice in my screenshot, that I have 1 warning because I didn’t set a static IP for the server yet. After installation completes, the system will automatically restart. You will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. When you login, you will then see in the Server Manager, that AD DS is now listed, along with DNS. Now all that you need to do is assign a static IP to your domain controller. To do this, in Server Manager, select Local Server from the panel on the left. From there, click on the Ethernet link labelled ‘IPv4 address assigned by DHCP, IPv6 enabled’. This will cause the Networks Connections explorer to open. From here, right click on the Ethernet network that is displayed. This is in fact the network connection that we configured when we first created the VM. On the Ethernet Properties dialog, select ‘Internet Protocol Version 4 (TCP/IPv4)’ and click the Properties button. Within the Internet Protocol Version 4 (TCP/IPv4) Properties dialog, enter a static IP, gateway, and DNS that is applicable to your network. Once all the items have been entered, click OK. You will also have to click Close on the Ethernet Properties dialog as well. Congratulations, you now have a domain setup in your lab environment. Add Systems to Your Domain Now that you have your domain setup, you need to add your other VM (the one that we will use for DPM) to the domain before being able to install DPM. Log into the system you want to add to the domain. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, select the Domain option for ‘Member of’, and enter the domain name you want to join and press OK. After pressing OK, you are immediately presented with a Windows Security dialog, in which you need to enter the credentials of an account that has Domain Admin rights. Enter the credentials and click OK. Once the system is successfully joined to the domain, you will receive the following Welcome message. Press OK. After you press OK to the Welcome message, you will receive a second prompt, indicating that you need to restart the system for the changes to take effect. You will be back on the System Properties dialog. Press Close. When you press Close, you will receive yet another prompt about restarting the system. You can choose to Restart Now or Restart Later, but you won’t be able to install DPM without the VM being added to the domain. After the system restarts, you will then be presented with the login screen. Something to note here, that because we were originally logged in with a local account, the first time you want to log on using a domain account you will have to type the domain\username; in my example SC\Administrator. Now we have our Active Directory server setup and ready, and the VM we will be installing DPM on is joined to the domain.
  20. Install the Operating System Now that we have created the VMs for our lab, we can install the Operating System (OS). Start by connecting to one of the VMs, either by double clicking on the VM in Hyper-V Manager, right click the VM and choose Connect, or click on Connect from the Action pane/menu. When you have the VM connection up, and an ISO mounted, power the VM on. On the Windows Setup screen, select the Language, Time/Currency Format, and Keyboard Method appropriate, and click Next. All you have to do now is click Install Now. Next you have to choose the Operating System and version you want to install. In our lab example, I will choose Windows Server 2012 Standard (Server with a GUI). Make your selection and then click Next. You will have to accept the license terms, and then click Next. For the Installation Type, since we don’t already have an OS installed, we will choose the ‘Custom: Install Windows only (advanced)’ option. Now select the hard drive that you want to install the OS to. Since we only created one hard drive when setting up the VM, we only have one to choose from. Select it, and click Next. Now all you have to do is wait for the installation to finish. Once the installation is complete, you will be prompted to enter a password for the local administrator account. This is different from a domain-based local administrator account. Enter a password and click Finish. After some final quick configuration, you will then be presented with the login screen. Now repeat these steps for the other VMs in the lab. NOTE: After you install an OS, you will need to rename the computer within the OS. To do this in Server 2012, launch Server Manager, and click on Local Server. Then click on the computer name. This will launch the System Properties dialog. From this dialog, click the Change button. From this dialog, enter the name you want to call the computer. In my lab, I called the Active Directory computer “AD”, and the Data Protection Manager computer “SCDPM”. Press OK after entering the name. You will encounter the following prompt. Click OK. Then click Close on the System Properties dialog. You can choose to either Restart Now or Restart Later, but the name change will not take effect until you do so.
  21. Introduction:I use Hyper-V in my LAB and that's what all these virtual machines will be running on. In my lab, I have Windows Server 2012 Datacenter installed as the server OS on the host machine. All other virtual machines will be running Windows Server 2012 Standard edition, with the graphical user interface (GUI). My hardware consists of the following: § Intel Xeon E5-2620 § Asus P90X79 WS § 64 GB G.Skill Ripjaws Z Series § 2 x 256 GB / 1 x 512 GB Samsung 840 Pro Series SSD § 1 x 150 GB HDD, and 1 x 250 GB HDD High Level PlanHere is a high level of what we are going to complete in this initial part of the series. 1. Create the Lab Environment 2. Install the Operating System 3. Install Active Directory Domain Services 4. Install SQL Server 5. Install System Center Data Protection Manager So now let’s start with the first part, system requirements and creating the lab environment. System RequirementsNote: The following page on TechNet describes the requirements for deploying Data Protection Manager. DPM server hardware requirements§ CPU: 2.33 GHz quad-core CPU § RAM: 8 GB § Pagefile: 0.2 percent of the combined size of all recovery point volumes, in addition to the minimum required size (1.5 times the amount of RAM on the computer). § Disk Space (DPM Install): DPM requires a minimum of 300 MB of free space on each protected volume for the change journal. Additionally, before archiving data to tape, DPM copies the file catalog to a DPM temporary installation location; therefore, we recommend that the volume on which DPM is installed contains 2–3 GB of free space. § Disk Space (Storage Pool): 2.5–3 times the size of the protected data § LUN: o Maximum of 17 TB for GUID partition table (GPT) dynamic disks o 2 TB for master boot record (MBR) disks Disk Requirements:The DPM storage pool disks cannot be .VHD – they must be either iSCSI attached disks or pass-through disks. The following types of disk configuration are supported as DPM storage pool: § Pass-through disk with host direct attached storage (DAS) § Pass-through iSCSI LUN which is attached to host. § Pass-through FC LUN which is attached to host. § iSCSI target LUN which is connected to DPM virtual machine directly. DPM server requirements§ You can install DPM on the same volume that the operating system is installed on, or you can install DPM on a different volume that does not include the operating system. § DPM server DPM is designed to run on a dedicated, single-purpose server. The DPM server should not be installed on any of the following: o A computer on which the Application Server role is installed. o A computer that is an Operations Manager management server o A computer on which Exchange Server is running. o A computer that is a cluster node. § DPM is not supported on the Turkish language version of any of the listed Windows Server versions. § The following prerequisites are required for installation: o Microsoft .NET Framework 3.5 with Service Pack 1 (SP1) o Microsoft Visual C++ 2008 Redistributable o Windows PowerShell 2.0 o Windows Installer 4.5 or later versions o Windows Single Instance Store (SIS) o Microsoft Application Error Reporting Setup automatically installs these if they are not already installed or enabled. If any pre-requisites cannot be installed during setup, or if you want to install them before you install DPM, you can install them manually. Create the Lab Environment: Hyper-V Configuration As mentioned, my environment uses Hyper-V. So, we’re going to start by configuring Hyper-V for our needs, and creating the Virtual Machines (VMs) required for our lab. The first thing we need to do is setup a Virtual Switch for the VMs to connect through. Launch Server Manager, click on Tools, and select Hyper-V Manager. When Hyper-V loads, it will have nothing in it. Even if we were to create a VM, it wouldn’t have a network connection to use. So we’ll start with creating a Virtual Switch. As you can from my screenshot, I have 2 LAN ports on my host. One of them has a connection to my home network and the Internet. In the Hyper-V Manager, click the Virtual Switch Manager from the Actions pane. Now, click on the Create Virtual Switch button. From here, you now need to configure the virtual switch that your VMs will use. Give it a name to clearly identify it (in my case I called it ‘External Network’), and choose the connection type. For more information about virtual networks, see the following TechNet article: http://technet.microsoft.com/en-us/library/cc816585(v=ws.10).aspx. Here is an excerpt from the article: External virtual networks. Use this type when you want to provide virtual machines with access to a physical network to communicate with externally located servers and clients. This type of virtual network also allows virtual machines on the same virtualization server to communicate with each other. This type of network may also be available for use by the management operating system, depending on how you configure the networking. (The management operating system runs the Hyper-V role.) For more information, see “A closer look at external virtual networks” later in this topic. Internal virtual networks. Use this type when you want to allow communication between virtual machines on the same virtualization server and between virtual machines and the management operating system. This type of virtual network is commonly used to build a test environment in which you need to connect to the virtual machines from the management operating system. An internal virtual network is not bound to a physical network adapter. As a result, an internal virtual network is isolated from all external network traffic. Private virtual networks. Use this type when you want to allow communication only between virtual machines on the same virtualization server. A private virtual network is not bound to a physical network adapter. A private virtual network is isolated from all external network traffic on the virtualization server, as well any network traffic between the management operating system and the external network. This type of network is useful when you need to create an isolated networking environment, such as an isolated test domain. For our demonstration, we are going to use an External Network so that the VMs can communicate with the Host system. Make all the appropriate selections and so forth, and then press OK. You may encounter the following warning message. This is because we are remotely connecting to the Host machine using the same network connection that we are about to setup as a Virtual Switch (hence selecting the ‘Allow management operating system to share this network adapter’ checkbox). Press ‘Yes’ to the dialog. Now that we have the virtual switch setup, we can start creating VMs for our lab. Create the Virtual Machines Let’s now create the VM’s we will need for the lab, specifically one for Active Directory, and another for DPM (since we are install all roles within the same server). In Hyper-V Manager, from the Actions pane, click on New and choose Virtual Machine. On the New Virtual Machine wizard beginning screen, click read the information presented and then click Next. Enter a name for the VM. Note that this is NOT the name the VM will have within the Operating System (unless you name it the same), but rather, used as an identifier in Hyper-V Manager. After you have entered a name, click Next. Now assign the amount of memory you want your VM to have, and then press Next. This is the screen where you connect your VM to the network that we created, then press Next. This is the screen where you configure how large a hard drive the VM will have. Make the appropriate customizations and click Next. For the Installation Options, choose if you will install an OS later, or if you want to use an ISO, then click Next. On the Summary screen, review your selections and entries, and click Finish. Once the VM is created, it will appear in the Hyper-V Manager. If you want to configure further settings, like the number of CPUs and mounting an OS ISO, right click on the VM and choose Settings or click on Settings from the Actions pane. Repeat these steps for each VM you need to create, in our case one for Active Directory and another for DPM. Here are the settings I have used for each of the VM’s: Active Directory: § Virtual Machine Name: AD § Memory: 2048 MB o NOTE: Active Directory doesn’t need 2 GB of RAM, it will run fine with 512 MB. I just increased the RAM so that the OS would install/respond faster during setup. § CPUs: 2 § OS: Windows Server 2012 SCDPM: § Virtual Machine Name: SCDPM § Memory: 8192 MB § CPUs: 4 § OS: Windows Server 2012
  22. So at this point we have Orchestrator setup and running, but we don’t have any runbooks yet. So, we are going to use the Sample Runbook from this TechNet article: Creating and Testing a Sample Runbook. The following topic describes how to create and test a simple runbook. The purpose of this runbook is to detect when a text file is added to a particular folder, copy that file to another folder, read the contents of the file, append a line from the copied file to another file, and then delete the original file. The runbook starts with a Monitor File activity to wait for the text file to be created. It then uses the Copy File, Read Line, Append Line, and Delete File activities to perform the other functions. A Junction activity is used to coordinate the activities so that the Copy File and Append Line activities are both completed before the source file is deleted. Creating the runbookUse the following procedures to create the runbook by using the required activities. To create a runbookClick Start, point to All Programs, click Microsoft System Center 2012, click Orchestrator, and then click Runbook Designer. In the Connections pane, right-click Runbooks to select New, and then click Runbook. A New Runbook tab appears at the top of the Runbook Designer Design workspace with the name New Runbook. Right-click the New Runbook tab to select Rename. Type Append and Copy Workflow in the Input box, and then press Enter. You have created a new runbook and are ready to begin adding and configuring activities. To add and configure a Monitor File activity With the newly created Append and Copy Workflow runbook open, in the Activities pane, expand the File Management category. Click and drag the Monitor File activity to the Runbook Designer Design workspace. Double-click the Monitor File activity to open its Properties dialog box. In the In folder box, type C:\Drop. In the Filters section, click the Add button. In the Filter Settings dialog box, in the Name list, select File Name. In the Relation list, select Matches Pattern. In the Value box, type *.txt. Click OK. Click the Triggers tab. In the Trigger if one of the files was section, select the Created check box, and then click Finish. The Monitor File activity is created and configured to watch for any new text files that are created in the C:\Drop folder. To add additional activities to the runbookIn the Activities pane, expand the File Management category. Click and drag the Copy File activity to the Runbook Designer Design workspace. Expand the Text File Management category. Click and drag the Read Line activity to the Runbook Designer Design workspace. To create a link between the Monitor File activity and the Copy File activity, click and drag the right arrow of the Monitor File activity to the Copy File activity. To create a link between the Monitor File activity and the Read Line activity, click and drag the right arrow of the Monitor File activity to the Read Line activity. By adding both the Read Line activity and the Copy File activity, you have created a workflow. To configure the Copy File activityIn the Append and Copy Workflow runbook, right-click the Copy File activity to select Properties. On the Details tab, right-click the File box to select Subscribe, and then click Published Data to open the Published Data dialog box. The Monitor File activity is listed at the top of the Published Data dialog box because this is the activity just before to the selected activity. In the Name column, select Name and path of the file, and then click OK. This populates the File property of the Copy File activity with the name of and path to the file from the Monitor File activity. In the destination Folder box, type C:\Copy. Click Finish. The Copy File activity is now configured to copy files from the source folder to the destination folder. To configure the Read Line activityIn the Append and Copy Workflow runbook, right-click the Read Line activity to select Properties. On the Details tab, right-click the File box to select Subscribe, and then click Published Data to open the Published Data dialog box. In the Activities list, select Monitor File. In the Name column, select Name and path of the file, and then click OK. Click the ellipse (…) button to the right of the File encoding box, and then select auto. In the Line numbers box, type 1-END, and then click Finish. The Read Line activity is now configured. To add an Append Line activityIn the Activities pane, expand the Text File Management category. Click and drag the Append Line activity to the Runbook Designer Design workspace to the right of the Read Line activity. To create a link from the Read Line activity to the Append Line activity, click and drag the right arrow of the Read Line activity to the Append Line activity. Right-click the Append Line activity to select Properties. On the Details tab in the File box, type C:\Copy\Masterlog.txt. Click the ellipse (…) button to the right of the File encoding box, and then select auto. Right-click the Text box to select Subscribe, and then click Published Data to open the Published Data dialog box. In the Name column for the Read Line activity, select Line text, and then click OK. Click Finish. The Append File activity is now configured to append files to the Masterlog.txt file. To synchronize branches of a runbookIn the Activities pane, expand the Runbook Control category. Click and drag the Junction icon to the Runbook Designer Design workspace. To create a link from the Append Line activity to the Junction activity, click and drag the right arrow of the Append Line activity to the Junction activity. To create a link from the Copy File activity to the Junction activity, click and drag the right arrow of the Copy File activity to the Junction activity. Right-click the Junction activity to select Properties. Click the ellipse (…) button next to the Return data from box, and then select Copy File. Click OK. This action configures the activity to return the same Published Data as the Copy File activity. Click Finish. The Junction activity is configured to coordinate the workflow so that no further activities run until both the Copy File activity and Append Line activity finish. To add and configure the Delete File activityIn the Activities pane, expand the File Management category. Click and drag the Delete File icon to the Runbook Designer Design workspace. To create a link from the Junction activity to the Delete File activity, click and drag the right arrow of the Junction activity to the Delete File activity. Right-click the Delete File activity to select Properties. Right-click the Path box to select Subscribe, and then click Published Data to open the Published Data dialog box. In the Activity list, select Copy File. In the Name column, select Name and path of the original file, and then click OK. Click Finish. The Append and Copy Workflow runbook is now completed. It should look similar to the following illustration. Testing the RunbookYou can test the runbook by using the Runbook Tester. This tool lets you run the entire runbook and inspect the completion status and output of each activity. The Runbook Tester runs the activities, so you must first create the folders specified for the runbook. To Test the RunbookCreate a folder on the runbook server called C:\Drop. Create a folder on the runbook server called C:\Copy. With the Append and Copy Workflow runbook selected in the Runbook Designer, on the toolbar, click Runbook Tester. Click Run. The Monitor File activity is loaded and waits for a text file to be created in the C:\Drop folder. Open Notepad and type a few lines of text. Save the file as C:\Drop\File1.txt. Wait a few moments for the other activities to run. Ensure that each of the activities is completed successfully. To view the Published Data and other details of an activity, click Show Details for the activity. Open the C:\Drop folder and ensure that the file has been removed. Open the C:\Copy folder and ensure that the file has been copied. Also verify that the MasterLog.txt file has the contents of the original file.
  23. Management Group Names Must be UniqueWhen you deploy both a Service Manager and data warehouse management server, you are asked to provide a management group name. You are also asked to provide a management group name when you deploy Operations Manager. The management group names that you use for the Service Manager management group, the data warehouse management group, and the Operations Manager management group must be unique. Important: If Operations Manager and Service Manager share the same management group name, you will have to reinstall the Service Manager management server. Because it is not possible to rename a management group, you will either have to completely reinstall Service Manager with a different management group name or choose not to manage your Service Manager installation with Operations Manager. Database CollationsYou must use the same supported language collations if you intend to import data from Operations Manager into Service Manager. However, this is true only for the OperationsManager database in Operations Manager and the SM DWStagingAndConfig database when you create an Operations Manager Data Source for the data warehouse. Specifically, this appears in the Service Manager console as a Data Warehouse Data Source. This does not affect either the System Center Operations Manager to System Center Service Manager Configuration Item connector or the System Center Operations Manager to System Center Service Manager Alert Incident connector. System Center 2012 – Operations ManagerSystem Center 2012 – Operations Manager is supported by Service Manager and Service Manager SP1 for connectors and agents. However, only corresponding System Center versions are supported when you register a data source in the Data Warehouse workspace. System Center 2012 – Operations Manager agents were not supported with System Center 2012 – Service Manager. However, the agent that is automatically installed by System Center 2012 – Service Manager SP1 is compatible with System Center 2012 – Operations Manager and System Center 2012 – Operations Manager SP1. After Service Manager Setup completes, you must manually configure the agent to communicate with the Operations Manager management server. To validate that the Operations Manager Agent was installed, open Control Panel and verify that the Operations Manager Agent is present. To manually configure the Operations Manager agent, see Configuring Agents. Changing the Account Configuration for an AgentYou can use the following procedure to change the account that the agent will use when performing actions requested by the management server. To change the account configuration for an agentOn the agent-managed computer, in Control Panel, double-click Operations Manager Agent. (In the category view of Control Panel in Windows Server 2008, Operations Manager Agent is in the System and Security category.) On the Management Group tab, select a management group and then click Edit. In the Agent Action Account section, edit the account information and then click OK.
  24. Before notifications are sent, first configure each notification channel, such as the settings for Simple Mail Transfer Protocol (SMTP). Notification messages are sent based on a notification template. Therefore, you must create a notification template. You can then use the Notification Subscription Wizard to subscribe a group of users to a notification that will be sent whenever the changes that you specify occur. Finally, you can verify that a notification is sent by manually generating the change. To configure email notificationsIn the Service Manager console, click Administration. In the Administration pane, expand Notifications, and then click Channels. In the Channels pane, click E-Mail Notification Channel. In the Tasks pane, under E-Mail Notification Channel, click Properties to open the Configure E-Mail Notification Channel dialog box. Select the Enable e-mail notifications check box. Click Add. In the Add SMTP Server dialog box, type the fully qualified domain name (FQDN) of the SMTP server that you want to use. In the Port number box, type or select the SMTP port number that you want to use. For example, select 25. In the Authentication method box, select either Anonymous or Windows Integrated. For example, select Anonymous. Then, click OK. In the Return e-mail address box, type the email address of the service account that is used during setup. In the Retry primary after box, type or select the number of seconds that you want Service Manager to wait before it tries to resend outgoing email notifications. For example, select 25. Click OK to close the dialog box. To validate email notification configurationIn the Channels pane, click E-Mail Notification Channel. In the Tasks pane, under E-Mail Notification Channel, click Properties to open the Configure E-Mail Notification Channel dialog box. Verify that the configuration you entered is correct. To create a notification template for incidentsIn the Service Manager console, click Administration. In the Administration pane, expand Notifications, and then click Templates. In the Tasks pane, under Templates, click Create E-mail Template. On the General page of the Create E-mail Notification Template Wizard, in the Notification template name box, type a name. For example, type New E-mail Incident Template. Optionally, in the Description box, you can type a description for the template that you are creating. Next to the Targeted class box, click Browse. In the Choose Class dialog box, click Incident, and then click OK. Make sure that an unsealed management pack of your choice is selected, and then click Next. On the Template Design page, in the Message subject box, type a subject for the email template. For example, type New Incident created with ID#. Then, click Insert. In the Select Property dialog box, select ID, and then click Add. In the Message body box, type a description to indicate that a new incident was opened for an email problem. Use the other default values on this page, and then click Next. On the Summary page, review the settings that you have selected for the template. Then, click Create. On the Completion page, click Close. To create a notification template for change requestsIn the Service Manager console, click Administration. In the Administration pane, expand Notifications, and then click Templates. In the Tasks pane, under Templates, click Create E-mail Template. On the General page of the Create E-mail Notification Template Wizard, in the Notification template name box, type a name. For example, type New Standard Change Request Received Template. Optionally, in the Description box, you can type a description for the template that you are creating. Next to the Targeted class box, click Browse. In the Choose Class dialog box, click Change Request, and then click OK. Make sure that an unsealed management pack of your choice is selected, and then click Next. On the Template Design page, in the Message subject box, type a subject for the email template. For example, type New Standard Change Request with ID#. Then, click Insert. In the Select Property dialog box, select ID, and then click Add. In the Message body box, type a description to indicate that a new standard change request was opened. Use the other default values on this page, and then click Next. On the Summary page, review the settings that you have selected for the template. Then, click Create. On the Completion page, click Close. To create a notification template for a newly assigned activityIn the Service Manager console, click Administration. In the Administration pane, expand Notifications, and then click Templates. In the Tasks pane, under Templates, click Create E-mail Template. On the General page of the Create E-mail Notification Template Wizard, in the Notification template name box, type a name. For example, type New Activity Assigned Received Template. Optionally, in the Description box, you can type a description for the template that you are creating. Next to the Targeted class box, click Browse. In the Select a Class dialog box, click Manual Activity, and then click OK. Make sure that an unsealed management pack of your choice is selected, and then click Next. On the Template Design page, in the Message subject box, type a subject for the email template. For example, type New Activity Assigned with ID#. Then, click Insert. In the Select Property dialog box, select ID, and then click Add. In the Message body box, type a description to indicate that an activity has been assigned. Use the other default values on this page, and then click Next. On the Summary page, review the settings that you have selected for the template. Then, click Create. On the Completion page, click Close. To validate template creationVerify that the new template you created appears in the list of notification templates. To create a notification subscription for an incidentIn the Service Manager console, click Administration. In the Administration pane, expand Notification, and then click Subscriptions. In the Tasks pane, click Create Subscription. On the Before You Begin page of the Create E-mail Notification Subscription Wizard, click Next. On the General page, in the Notification subscription name box, type a name. For example, type New Incident for E-mail Problem Notification Subscription. Optionally, in the Description box, you can type a description for the subscription that you are creating. Next to the Targeted class box, click Browse. In the Choose Class dialog box, choose a class. For example, click Incident. Then, click OK. In the When to notify box, select When an object of the selected class is created. Make sure that an unsealed management pack of your choice is selected, and then click Next. On the Additional Criteria page, select Incident. In the Available Properties list, select Classification Category, and then click Add. On the Additional Criteria page, click the Criteria tab. In the Criteria area, next to [incident] Classification Category, select equals. In the list, select E-mail Problems, and then click Next. On the Template page, next to the E-mail template box, click Select. In the Select Objects dialog box, in the Templates list, select a notification template. For example, select New E-mail Incident Template, click OK, and then click Next. On the Recipient page, click Add. In the Select Objects dialog box, search for the appropriate user, and then select the user. Click Add, click OK, and then click Next. For example, select the user account for a messaging analyst or messaging administrator. NOTE: The notification address must be configured for the user account of the messaging analyst or messaging administrator. On the Related Recipients page, click Add. In the Select Related Recipient dialog box, search for the appropriate class, and then select the appropriate substitution string that represents the user. Click Add, click OK, and then click Next. For example, select additional user accounts that you want to send the notification to. On the Summary page, review the settings that you selected for the notification subscription, and then click Create. On the Completion page, click Close. To create a periodic notification subscription for a release recordIn the Service Manager console, click Administration. In the Administration pane, expand Notifications, and then click Subscriptions. In the Tasks pane, click Create Subscription. On the Before You Begin page of the Create E-mail Notification Subscription Wizard, click Next. On the General page, in the Notification subscription name box, type a name. For example, type Daily Notification for Deploy HR Web 2.0 Release Record. Optionally, in the Description box, you can type a description for the subscription that you are creating. For example, type This subscription sends a daily notification of the status for the HR Web 2.0 release record. In the When to notify box, select Periodically notify when objects meet a criteria. Next to the Targeted class box, click Browse. In the Choose Class dialog box, choose a class, and then click OK. For example, click Release Record. Make sure that an unsealed management pack of your choice is selected, and then click Next. On the Additional Criteria page, select Release Record. In the Available Properties list, select Status, and then click Add. In the Criteria area, next to [Release Record] Status, select does not equal. In the list, select Closed, and then click Next. On the Recurring Notification page under Recurrence pattern, select Notify every <TimeInterval> and then choose an interval. For example, set the recurrence pattern to every 1 day. On the Recurring Notification page under Range of recurrence, select a range of recurrence or choose no end date. For example, select No end date. On the Template page, next to the E-mail template box, click Select. In the Select Template dialog box, in the Templates list, select a notification template that you have created for release record notifications. On the Recipient page, click Add. In the Select Objects dialog box, search for the appropriate user, and then select the user. Click Add, click OK, and then click Next. For example, select the user account for the release manager. NOTE: The notification address must be configured for the user account of the messaging analyst or messaging administrator. On the Related Recipients page, click Add. In the Select Related Recipient dialog box, search for the appropriate class, and then select the appropriate substitution string that represents the user. Click Add, click OK, and then click Next. For example, select additional user accounts that you want to send the notification to. On the Summary page, review the settings that you selected for the notification subscription, and then click Create. On the Completion page, click Close. To validate a notification subscriptionLocate the notification subscription that you created in the list of subscriptions. To verify a notification configurationIn the Service Manager console, click Work Items. In the Work Items pane, expand Work Items, expand Incident Management, and then click All Open Incidents. In the Tasks pane, under Incident Management, click Create Incident. In the Incident <Number> New form, enter the required information in the Affected user, Title, Classification Category, Impact, and Urgency boxes. In the Classification Category list, select E-mail Problems, and then click OK. Verify that an email notification that contains the information you entered in the template is received. The email title should contain the incident ID number. To create a messaging-enabled universal security groupIn the Exchange Management Console, navigate to Recipient Configuration, right-click Distribution Group, and then click New Distribution Group. On the Introduction page, either choose an existing universal group or create a new group. On the Group Information page, select the Security group type. Complete the creation of the group. Add members to the group by right-clicking them, clicking Properties, and accessing the Members tab. Wait for Service Manager to sync with Active Directory Domain Services (AD DS), or perform a manual Synchronization from Administration>Connectors. (Click AD Connector, and then click the Synchronize Now task on the right-hand side). Once the Active Directory synchronization has completed, the newly created group will be available as a configuration item in Service Manager, and it can be selected in the user picker fields, such as Affected User and Assigned To. To create a workflow to notify stakeholders when an incident is createdNavigate to Administration > Workflows > Configuration. Double-click Incident Event Workflow Configuration. Click Add, and then click Next on the Before you Begin page. Give the workflow a name, such as “Incident Created – Email Stakeholders”. Leave the default of When an incident is created in the Check for Events drop-down list. Select one of your custom management packs (or create one) to store the workflow in, and then click Next. Click Next on the Specify Incident Criteria page. (We want this workflow to run when any new incident is created.) Optionally, apply a template. (In this case we are creating the workflow for notification only, so we choose Do not apply a template.) In the Select People to Notify dialog box, select the Enable notification check box. Add the appropriate users you want to notify with the appropriate templates. Click Next, and then click Create to complete creation of the workflow. To test the workflow and mail the enabled universal security group Create an incident and assign it to the messaging-enabled universal security group that you created earlier.Before notifications are sent, first configure each notification channel, such as the settings for Simple Mail Transfer Protocol (SMTP). Notification messages are sent based on a notification template. Therefore, you must create a notification template. You can then use the Notification Subscription Wizard to subscribe a group of users to a notification that will be sent whenever the changes that you specify occur. Finally, you can verify that a notification is sent by manually generating the change.
  25. To create a System Center Virtual Machine Manager connectorIn the Service Manager console, click Administration. In the Administration pane, expand Administration, and then click Connectors. In the Tasks pane, under Connectors, click Create Connector, and then click Virtual Machine Manager connector. Complete these steps to complete the Virtual Machine Manager Connector Wizard: On the Before You Begin page, click Next. On the General page, in the Name box, type a name for the new connector. Make sure that Enable this connector is selected, and then click Next. On the Connection page, in the Server Information area, type the same of the computer hosting Virtual Machine Manager (VMM). On the Connection page, in the Credentials area, either select an existing account or click New, and then do the following: In the Run As Account dialog box, in the Display name box, type a name for the Run As account. In the Account list, select Windows Account. Enter the credentials for an account that has rights to connect VMM, and then click OK. On the Connection page, click Test Connection. In the Test Connection dialog box, make sure that The connection to the server was successful appears, and then click OK. On the Connection page, click Next. On the Summary page, make sure that the settings are correct, and then click Create. On the Completion page, make sure that you receive a “Virtual Machine Manager connector successfully created” message, and then click Close. To validate the creation of a System Center Virtual Machine Manager connectorIn the Connectors pane, locate the System Center Virtual Machine Manager connector that you created. Review the Status column for a status of Running. NOTE: Allow sufficient time for the import process to finish if you are importing a large number of virtual machines or clouds. In the Service Manager console, click Configuration Items. In the Tasks pane, click Create Folder. In the Create New Folder Wizard, do the following: In the Folder name box, type a name for the folder. For example, type Test. In the Management pack area, make sure that an unsealed management pack of your choice is selected, and then click OK. For example, select Service Catalog Generic Incident Request. In the Configuration Items pane, click the folder you just created. For example, click Test. In the Tasks pane, click Create View. In the Create View Wizard, do the following: On the General page, in the Name area, type a name for this view. For example, type VMMTemplates. In the Management pack area, make sure that an unsealed management pack of your choice is selected. For example, select Service Catalog Generic Incident Request. In the navigation pane of the wizard, click Criteria. In the Advanced Search area, click Browse. In the drop-down list (located to the right of the Type to filter box), select All basic classes. In the Type to filter box, type virtual machine template, click Virtual Machine Template, click OK, and then click OK to save and close the form. In the Configuration Items pane, expand the folder you created, and then click the view you created. For example, expand Test, and then click VMMTemplates In the VMMTemplates pane, you will see the Virtual Machine Manager templates that have been created.
×
×
  • Create New...