Please find the Screenshot attached.

Replication Report or Summary

Based on my experience I have inputted the 3 options to generate total Data Replication report

Option: 1

-->login to Datadomain web GUI http://<storagename> press enter

-->Click on Storage Server

--> Click on Replication

-->if DDboost, Click on DDboost

-->Click on File Replication

-->select the Duration

--> there you can find the total Replication size in 24 hrs

Option: 2

-->login to Datadomain web GUI http://<storagename> press enter

-->On left bottom, click on report,

--> Select replicationSummary --> select duration --> click on create

Option: 3 opscenter

-->Click on Report

-->Click on New Custom Report

• Select Ranking

àSelect Duration

àSelect Master server if any in particular

àUnder Disk please select Storage server name or Disk Volume name if you looking for any specific

Select Report on: “Disk Volume Name” or Storage Server Name

y-axis Display name

Select Report Data: “Disk Volume Replication “

Select Count

Select time basis as “Job End Time”

Click on Next

After clicking next you will get the report based on Disk volume name and Disk Replication Count in form on Ranking

Click next to save

After Save, open report and click on “show chart as Table”

A table will pop up with all values

Introduction

This is the third of an informal series on how to keep your enterprise environment secure using often-overlooked capabilities of Symantec Endpoint Protection (and the OS upon which it functions). 

• The first article, Using SEPM Alerts and Reports to Combat a Malware Outbreak, demonstrated how to use reporting features of SEP 12.1's SONAR component to identify Suspicious files for which there were no AntiVirus signatures yet created.
• The second, Recovering Ransomlocked Files Using Built-In Windows Tools, deals with a few possible ways how to prevent and recover from one of today's most-destructive threats, should it infect your network and hold your data hostage.

This third article illustrates how Symantec Endpoint Protection's optional Intrusion Prevention System (IPS) component can help security admins keep their organization secure and track down infected computers on the network.

IP What?

Unlike AntiVirus, which looks for known malicious files, IPS scans the network traffic stream in order to find threats using known exploits and attack vectors. IPS does not detect specific files, but rather specific methods that can be used to get malicious files onto your network. This allows IPS to protect against both known and unknown threats, even before antivirus signatures can be created for them.  It’s very cool.

SEP’s IPS component greatly increases the number of threats that can be blocked, so the use of IPS is strongly recommended on almost all endpoints.  More details are contained in:

Best practices regarding Intrusion Prevention System technology
http://www.symantec.com/docs/TECH95347

Not Just for Windows Any More!

IPS has been an optional component of SEP for Windows since the beginning.  In order to enable IPS in Symantec Endpoint Protection 11.x, the client firewall portion (Network Threat Protection) must be installed and running. In SEP 12.1, the client firewall function is separate and does not need to be installed or enabled for IPS to function. 

SEP 12.1 RU4 brought many new features to the SEP client that runs on Macintosh (“SEP for Mac”).  An overview of these enhancements can be found in:

Overview for Symantec Endpoint Protection 12.1.4 for Mac
http://www.symantec.com/docs/HOWTO92146

One of the best of these enhancements is that IPS can now defend Mac machines as well as the Windows boxes on the network.  So, definitely upgrade the protection on your Macs!

How IPS Defends Clients

For an excellent illustration of how IPS can protect against a very dangerous threat, see Recovering Ransomlocked Files Using Built-In Windows Tools.  Even if the initial Trojan.Cryptolocker .exe is not detected by SEP’s AntiVirus components, IPS attack signatures can still block the network traffic that this threat relies upon in order to generate the keys necessary to sabotage a computer’s files.  If you see a pop-up “System Infected: Trojan.Cryptolocker” then IPS has just blocked the Trojan’s network activity (and saved you a load of grief).  Get that computer isolated and perform a load point diagnostic to identify any unidentified malware files!

Generating SEPM Reports of Network Attacks

As detailed in my first article, your Symantec Endpoint Protection Manager contains advanced capabilities for reporting and alerting.  It can often tell you exactly what is going on with the security of your network, if you know how to look.

One report that it can generate on demand is Network Threat Protection: Attacks.  (Remember: in SEP 12.1, it is not necessary to have the NTP component of SEP installed in order to take advantage of IPS.  IPS can be installed without NTP.  The report of all IPS attacks is still listed under Network Threat Protection as a legacy inherited from SEP 11 days.)

Just click on Monitors, Logs tab, and pick the "Network Threat Protection" option for Log type.  Choose “Attacks” to see all the IPS events that have occurred on managed SEP clients and been forwarded to the SEPM.

The logs for all the attack events will be displayed on screen, and can be exported for more advanced parsing and analysis with your favorite spreadsheet program. 

Identifying Unprotected Computers

One example of how these can be useful: in a recent real-world case, an administrator had been fighting a never-ending battle to eradicate W32.Downadup from the corporate network.  There were constant detections of this threat being stopped, but somewhere out there were infected computers which constantly tried to re-infect others.  Examining the Risk Reports failed to show any instances where the threat was being detected by AV but “left alone,” so where were they?

Examining the exported Network Attack logs, it was pretty clear that IPS was also blocking infection attempts (traffic that attempted exploit of the vulnerability that W32.Downadup uses to spread).  These logs, though, showed what IP addresses involved with each “[SID: 23179] OS Attack: MSRPC Server Service RPC CVE-2008-4250 attack blocked. Traffic has been blocked for this application: SYSTEM”

Examining the Remote Hosts that were responsible for all that traffic was the solution to this case.  There were a handful of infected computers that had no AV product on them at all. Installing SEP ended the persistent W32.Downadup troubles for good. 

Identifying Infected Machines

In another recent real-world example: hundreds of Auto-Protect virus events (Event ID 51) were seen on the shared directory of a file server.  Several days were spent examining the load points of the server itself, with nothing malicious found.  The reason: the infection was on one of the 400 clients which connect daily to that mapped drive.  Some client in the network had attempted to do the damage- but which one?  It would not be possible to examine load point diagnostics from all those hundreds of clients.

Luckily, that file server had IPS installed.  The IPS logs were examined and a large number of ”Incoming Auto-Block Event” entries were spotted, coming from one particular IP Address.  This activity might have been a coincidence, but in this case it was a very big clue as to which mapped client was infected.  That computer was isolated, cleaned, patched and returned to the network.  Problem solved.  

. 

Conclusion

IPS can protect your computers- and everything on them-  in ways that AV alone cannot.  And, its logs can provide valuable intelligence about which computers in the network are infected. 

Moral of this story: it’s much easier to deploy the SEP IPS client and read its logs than to examine 400 load point diagnostics.  &: )

One final recommendation: it is always a good time to ensure that the organization's defenses are in good order. There is a great deal of malware in circulation, and it is guaranteed that tomorrow the baddies will come up with new code and techniques.  Take precautions now!

Symantec Endpoint Protection – Best Practices
http://www.symantec.com/theme.jsp?themeid=stopping_malware&depthpath=0

Many thanks for reading!  Please do leave comments and feedback below. 

In questo articolo sono elencati una serie di comandi e funzioni di sistema che consentono di personalizzare diversi aspetti del sistema operativo e del suo comportamento nelle singole sessioni utente.

La grande maggioranza di queste funzioni è richiamabile da menu di sistema operativo, da menu di sistema contestuali oppure dal pannello di controllo, ma utilizzando il nome del comando è possibile agire direttamente sulla funzione desiderata risparmiarmiando tempo per la sua ricerca.

Inoltre, una buona parte di queste funzioni sono utilizzabili all'interno di programmi batch, ad esempio inserendo alcuni di questi comandi con dei parametri specifici è possibile personalizzare vari aspetti del sistema operativo.

Nota : i comandi elencati sono per la maggior parte compatibili anche con i sistemi operativi Windows 7, Vista e Windows XP.

Per eseguire uno di questi comandi, da Esegui ( Tasto Windows + R  ) digitare uno dei comandi elencati nella colonna Comandi :

We're please to announce support for OS X 10.9 Mavericks. More details can be found here:

https://www-secure.symantec.com/connect/articles/it-management-suite-os-platform-support

V-79-57344-33967 - Snapshot Technology: Initialization failure on: "Search instance\Search-DB 1 (Sharepoint\WSS_Search_Sharepoint)". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE00084AF): The directory or file was not found, or could not be accessed. Check the Windows Event Viewer for details.

Windows Event Viewer information

Event ID : 8193
Source : VSS
Error : ConvertStringSidToSid(S-1-5-80-1202657632-534270475-2053275915-3193571600-3895445954.bak), 0x80070539, The security ID structure is invalid.
 

Cause
Invalid security ID structure

Solution

1)Open regedit on remote server

2)Navigate to HKLM\Software\Microsoft\Windows NT\Current Version\Profile List

3)Right click on Profile list and click Export to take a backup of the registry and save it

4)Look for the invalid SID that is listed in the event viewer (S-1-5-80-1202657632-534270475-2053275915-3193571600-3895445954.bak) and delete it.

5)Restart the remote server and run the backup again.
 

Often times when software is purchased for an organization, the vendor provides a license key or user ID and password combination to activate their software.

Customers often store this information in spreadsheets on their local computer or on a file share within their organization. This can lead to lost information when it is not linked to the consumption of licenses within the organization.

By using the Symantec Management Platform with Asset Management Suite, a customer can simply extend the out-of-the-box solution and create a central repository for such information that also links to purchase information; individual licenses; and actual consumption of such licenses. 

The attached document outlines the necessary steps to add data classes; modify a Resource Type; and create a data entry screen for storing license keys, usernames, and passwords (in clear text).

Trying to wade through Client Activity logs can become a tedious task, especially when you have thousands of clients. I would like to show you some advanced filtering that you can do to get the Client info you need much more quickly.

For this article, I will focus solely on the Client Activity logs in the SEPM:

The box we want to use for filtering is the Event source box. There are specific keywords you can use to get more granular. They are as follows:

1.     GUP
2.     IPS
3.     LiveUpdate Manager
4.     Network Intrusion Protection Sys
5.     REP
6.     Smc
7.     SONAR
8.     SYLINK
9.     Symantec AntiVirus
10.     Symantec Endpoint Protection

To look at events generated by SMC, we enter SMC into the Event source box:

Click View Log to see those events

As you can see, a wealth of info is generated. This also holds true for the other nine keywords above as well. I highly recommend you try these out to see what info comes back. It is very detailed and you may find somethings that you previously did not know about! Better yet, you can export to CSV and drop into Excel and filter as needed.

I hope these help you in your daily monitoring tasks. Feel free to post and comments/questions/criticisms

Thanks!
Brian

Additional questions

If you have any problems with your set up, please contact your BCAM.
 

Additional Alternative Notification Methods

You may also want to subscribe to anti-virus RSS feeds by visiting the following link and signing up for the virus definitions and security updates: http://www.symantec.com/xml/rss/definitions.jsp 

Symantec Workspace Streaming SDK includes several web services. You can access them by using the Simple Object Access Protocol (SOAP). A Web Services Description Language (WSLD) document exposes the interface. The WSLD document provides details on the published methods and objects. The Workspace Streaming web services are separated into multiple areas of management. Each area has its own WSDL file.

This Quick Start Guide explains you through developing clients in the Visual Basic and Java languages. However, most programming languages, such as C#, Visual Basic, C++, Java, and Python, provide support for SOAP web services. Most languages also let you use the WSLD document to automatically generate proxy classes.

You must meet the following requirements to use the Symantec Workspace Streaming SDK:

• The Workspace Streaming web services require Workspace Streaming 6.1 or later.
• Applications accessing the web services must be able to contact the server that hosts the Streaming Console.
• You must have an account on your Workspace Streaming system.

Thanks,

Ankit Shrivastava

Are you using Yahoo Mail as your primary contact email or email client for receiving Connect notifications and find that a lot of your messages are being delivered to the Spam folder?

Yahoo is inconsistent - messages from Connect will be delivered to your Inbox AND to your Spam folder. Just to be on the safe side, check that Spam folder to see what's piling up in there. It can't all be cheap pharmaceuticals!

Creating a filter that will deliver your Connect messages to the Inbox is a simple task - then you won't need to check your Spam folder for our messages ever again!

First you need to start with a message from us that has landed in your Spam folder that you know is a legitimate Connect message. Go right ahead and open it. It never hurts to add us to your Contacts list but don't get distracted - we're creating a Filter.

Open your Spam Folder and look for a message from Connect - it could be a notification or a newsletter.

Open any one of these messages and then choose the "More..." icon

A drop down menu will open with a list of options. Choose "Filter Email Like This..."

A box will open allowing you to customize your filter

All you need to do is choose "Inbox" in the drop down menu under "Then move the message to" and click "Save"

Unlike Gmail, messages currently in your Spam folder that would be affected by this filter won't be delivered to your inbox. It only applies to messages delivered after the filter has been created. You're still going to have to crawl through your spam folder looking for important messages.

For IT Analytics reports hosted by SQL Server Reporting Services (which include out-of-the-box reports and dashbaords) some users may experience extended wait times before the report is able to render, and in some cases the report may even fail or timeout. This typically occurs in environments where there are extremely large data volumes and where reports are pre-configured to display all data by default (without filtering).

To minimize the time it takes for some IT Analytics reports to load, steps can be taken to configure settings so that data will be filtered by default, hence greatly improving performance. This article will describe such process, utilizing Microsoft Report Builder a client side aplpication which comes with SQL Server Reporting Services.

Selecting the Report

1. To load Report Builder, open Symantec Management Platform Console and navigate to: Settings > Notification Server > IT Analytics Settings > Reports > Report Builder. Then click on the Launch Report Builder button.

​

2. If prompted, click Run to start downloading the application.
3. Be patient, launching application may take a minute or two, depending on connectivity. While the application is loading, you should see this message:

4. Click Open to select the report you want to optimize. Under the default configuration, all IT Analytics reports are stored within the ITAnalytics folder off the ReportServer root. 

NOTE: For the purposes of this example, we will select the IT Analytics Configuration Events report. As such, the parameters you select in the next section of this article may be different.

Modifying the Report

1. When report opens, expand Parameters in the Report Data pane on the left, then right-click the From parameter and select Parameter Properties.

2. Navigte to Default Values > Get values from a query. For both fields select MaxDate from drop-down list, then click OK.

3. Modify the properties for the Types parameter and navigate again to Default Values. Select Specify Values and Add new value. In the field type in 'Cube Processing' (without quotes) as shown below, then click OK. If you are modifying a different report, select an appropriate paramater and input a default value that matches a value for that parameter.

5. Click Save to apply all changes (saving may take couple seconds).

Reloading the Report

1. In the Symantec Management Console, navigate to Reports > IT Analytics > Reports > IT Analytics Events > ITA Configuration Events (or a the appropriate report you modified). Refresh the browser if necessary. You should notice the report load much faster than previously.
2. Verify that the current day (in the From parameter) and the specific Type and Target are pre-selected with the values we input previously (or the appropriate values you entered if modifying a different report).

3. To adjust the parameter values, you can select different values as you normally would.

By default, reports and dashboards in IT Analytics (hosted by SQL Server Reporting Services) will run automatically when selected. This behavior can sometimes be problematic for environments with excessive amounts of data, resulting in increased load times or timeouts for certain reports. One option to prevent this is to modify the value of a parameter within a report so that it does not execute automatically when clicked, a process which is documented in the article below.

To modify report parameters in more detail in order to load reports more efficiently, please see the article: Modifying IT Analytics Reports to Decrease Load Times.

1. For the purposes of this example we will use the DLP Endpoint Incident Search report. Note that by default, the report runs with the Policy Name parameter value of 'All' pre-selected.

2. To change this report, open a browser on the server hosing SQL Reporting Services and goto: http://localhost/Reports.
3. From within the IT Analytics folder, locate and hover over the DLP Endpoint Incident Search report (or the report you want to modify) and to the right you will see a menu of options. Select Manage.

4. Once in the report manage screen, select the Parameters section.

5. Once there, uncheck the 'Has Default' column from the parameter you want to force users to select or enter information on. This will ensure a user must select a value for that parameter before the report can be executed. In this example we will use the Policy Name parameter, then click Apply.

6. Return to the Symantec Management console to load the report and you should notice that it does not automatically execute the report, but instead prompts for a parameter value. Once a value is selected click View Report. Refresh the browser if necessary. 

Symantec Data Loss Prevention provides many operational log files that can be used to interpret how the system is running.

The default locations put the log files during installation for the Enforce Server and Detection Servers on the computers that host the servers. The files are in the \SymantecDLP\Protect\logs directory on Windows installations and in the /var/log/SymantecDLP directory on Linux installations. The number at the end of the log file name indicates the count.

Most log files are located on the sub-directory: \SymantecDLP\Protect\logs\debug on Windows and /var/log/SymantecDLP/debug on Linux.

For IT Analytics reports hosted by SQL Server Reporting Services (which include out-of-the-box reports and dashbaords) some users may experience extended wait times before the report is able to render, and in some cases the report may even fail or timeout. This typically occurs in environments where there are extremely large data volumes and where reports are pre-configured to display all data by default (without filtering).

To minimize the time it takes for some IT Analytics reports to load, steps can be taken to configure settings so that data will be filtered by default, hence greatly improving performance. This article will describe such process, utilizing Microsoft Report Builder a client side application which comes with SQL Server Reporting Services.

Selecting the Report

1. To load Report Builder, open Symantec Management Platform Console and navigate to: Settings > Notification Server > IT Analytics Settings > Reports > Report Builder. Then click on the Launch Report Builder button.

​

2. If prompted, click Run to start downloading the application.
3. Be patient, launching application may take a minute or two, depending on connectivity. While the application is loading, you should see this message:

4. Click Open to select the report you want to optimize. Under the default configuration, all IT Analytics reports are stored within the ITAnalytics folder off the ReportServer root. 

NOTE: For the purposes of this example, we will select the IT Analytics Configuration Events report. As such, the parameters you select in the next section of this article may be different.

Modifying the Report

1. When report opens, expand Parameters in the Report Data pane on the left, then right-click the From parameter and select Parameter Properties.

2. Navigate to Default Values > Get values from a query. For both fields select MaxDate from drop-down list, then click OK.

3. Modify the properties for the Types parameter and navigate again to Default Values. Select Specify Values and Add new value. In the field type in 'Cube Processing' (without quotes) as shown below, then click OK. If you are modifying a different report, select an appropriate parameter and input a default value that matches a value for that parameter.

5. Click Save to apply all changes (saving may take couple seconds).

Reloading the Report

1. In the Symantec Management Console, navigate to Reports > IT Analytics > Reports > IT Analytics Events > ITA Configuration Events (or a the appropriate report you modified). Refresh the browser if necessary. You should notice the report load much faster than previously.
2. Verify that the current day (in the From parameter) and the specific Type and Target are pre-selected with the values we input previously (or the appropriate values you entered if modifying a different report).

3. To adjust the parameter values, you can select different values as you normally would.

Create a Deployment Solution 7.5 Boot Disk

Reviewing the Symantec Deployment Solution User guide for 7.5 listed here www.symantec.com/business/support/index?page=content&id=DOC5678 there isn’t clear instructions for using Boot Disk Creator, just that it exists.  I would assume this is because they feel a majority will be using PXE/Symantec Netboot Services.    For now, our organization still relies on boot disks as a CD or USB drive.  Depending on the systems you are deploying images to that you know how to create both.

Boot disk creator will run remotely, albeit slowly, if you have access to the location that it is installed.  If you do not have physical network access, ask your network admin to make the location a shared folder so that you can run it remotely. 

Why will you have to run it remotely?  Aside from access issues, in our case the NS is a virtual server and it’s not just a case of walking up to it in your data center and plugging in the USB drive and vsphere, is very limited on what it can access as far as clipboard and hardware on a tech's computer and connecting those to VMs.  If you do not need to create a USB disk, and prefer an ISO it will be in the best interest of time and resources to be logged in directly to the NS through RDP, or other remote access software, and running boot disk creator locally to the NS.

Before we get started there are a few things to think about:

• The pre-boot environment used in DS 7.5 is WinPE 4.0.  This means that if you have drivers that Symantec didn’t preload for you, you will need to have them ready when we get to the part of adding drivers to the driver database.
• If you require anything other than DHCP for your Automation environment, you will either need to know how to reconfigure this with cmd line (after it tries for a decade to configure DHCP in automation) or tinker around with it in Boot disk creator.

The install on the NS path for boot disk creator is

<Install Directory>\Program

Files\Altiris\Deployment\BDC\Bootwiz\bootwiz.exe

The NS, and I understand why even if I dont like it, is the only location for boot disk creator in 7.5.  In 7.1 it was available on any deployment server via the deployment share, however in the new environment the deployment share no longer exists on task & package servers. Well, sort of, you may find it here:

\\ Program Files\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{guid}\cache\bootwiz

Changes made to Boot Disk Creator on Task Servers, or if you copy the bootwiz directory to your technician computer and run it there, do not affect the NS. 

OK, on with the show!  Open bootwiz.exe.  You may have to run it from an admin level command prompt. 

Boot Disk Creator Wizard starts…

If you haven’t run the creator yet, you will want to choose “Create a new…” Otherwise, go to the interface and edit a previous configuration.

With a New configuration Fill in the blanks, Select your OS and OEM extensions:

At this point you wait for the driver database to be opened up.  If you haven’t already, disable any IPS software.  McAfee HIPS doesn’t like boot disk creator very much.  This is a problem if you are executing bootwiz from a remote system and will prevent you from going any further. The wait time for the driver database to open can take any unkown amount of time depending on whether you are accessing bootwiz remotely, or the resources available on the NS.

Once opened, this is where you can review what drivers will be loaded in your boot disk.

If you have to add any, select Have Disk…  If you are building your images in vmware products you will need to add drivers for those here.  The drivers can be found on any system that has vmware tools installed.  You shouldn’t have a problem with any Intel E1000 NIC’s, but I did have to add a driver for VMXNET3 and PVSCSI (Para virtual SCSI) to my boot disk in order to capture images from machines I had built in VSPHERE.  Since my NS has vmware tools installed, I was able to grab the drivers lfrom the NS itself.  Make sure you add drivers that are compatible with Winpe 4.0  & match the architecture.  Vmware drivers can be found in these folders according to vmware's own documentation:

Click next and you will have the option of selecting DHCP or Static for your boot disc.  For capturing one particular image I needed a static IP address and this will all depend on your enviroment.  Most will use DHCP.  Static selection presented some problems for me because the bat file generated for the static option didn’t work as well as i thought it would because the network device on my vm that I wanted to capture didn’t use the same name that is written in to the bat. Fortunately, you can modify this later.

Click next and wait again. Add any optional components here…

And lastly, review and finish!

As I mentioned, if you do decide to go static for your network adapter, you may have to modify it.  The default name that Symantec had written in didn’t match my VM and so I changed it here.  You can also just use DHCP, wait an hour for it to time out and then type the commands in manually yourself and then once configured properly rerun runagent.bat once in automation.

Once you are ready to make your boot disk right click on the configuration you made and select “Create Boot Disk”

Select the values you prefer.  Some systems you will need an ISO, and some a USB, some it doesn’t matter.  I always run through twice and make both so that I have them.  Also, select the compatible processor and select next.

If you select USB, you will have to make sure it detects the right drive before you continue. 

From here it will start to compile

Once done either burn or mount and test!

Once you are confident in you are boot disk you created you can make more.You can use the ISO to burn more CD's, or you can can capture a GHO image file of your USB boot disk using ghost.exe and imaging more USB drives with that GHO image file.  Also, using ghost explorer you can then add files and folders to your GHO image as time goes on, just keep in mind the size of the USB drive you are using and to not go over it.

By default, reports and dashboards in IT Analytics (hosted by SQL Server Reporting Services) will run automatically when selected. This behavior can sometimes be problematic for environments with excessive amounts of data, resulting in increased load times or timeouts for certain reports. One option to prevent this is to modify the value of a parameter within a report so that it does not execute automatically when clicked, a process which is documented in the article below.

To modify report parameters in more detail in order to load reports more efficiently, please see the article: Modifying IT Analytics Reports to Decrease Load Times.

1. For the purposes of this example we will use the Asset Search report. Note that by default, the report runs with the Asset Type parameter value of 'All' pre-selected.

2. To change this report, open a browser on the server hosing SQL Reporting Services and goto: http://localhost/Reports.
3. From within the IT Analytics folder, locate and hover over the Asset Search report (or the report you want to modify) and to the right you will see a menu of options. Select Manage.

4. Once in the report manage screen, select the Parameters section.

5. Once there, uncheck the 'Has Default' column from the parameter you want to force users to select or enter information on. This will ensure a user must select a value for that parameter before the report can be executed. In this example we will use the Asset Type parameter, then click Apply.

6. Return to the Symantec Management console to load the report and you should notice that it does not automatically execute the report, but instead prompts for a parameter value. Once a value is selected click View Report. Refresh the browser if necessary. 

Application and infrastructure availability is a key consideration in today's modern business continuity strategies for SAP cloud infrastructures stretched across distances. In traditional infrastructure designs for SAP high availability, workloads across physical data centers are disrupted when any of the infrastructure components fail at the same time. These traditional high availability designs are limited and usually require special combinations of software and hardware that are operating system specific, database specific, or both, making them complex, inflexible, costly, and difficult to implement and maintain. Often these designs require more effort to keep them running than actually providing the required protection and availability promised in the first place.

This white paper focuses on High Availability and Application Mobility add-on bundle of the on-premise Cloud-enabled Infrastructure for SAP. It explains the transformation of a single datacenter into a mission-critical business continuity solution with active/active datacenters. The solution is enabled by EMC®VPLEX® Metro, EMC Symmetrix® VMAX®, VMware vCloud Suite, and VMware vSphere Metro Storage Cluster (vMSC) with Symantec ApplicationHA, VMware vSphere HA and DRS.

Symantec ApplicationHA provides application monitoring and restart within virtual machines. For the scope of this paper, Symantec ApplicationHA simplifies and centralizes application administration and management through integration with VMware vSphere and guest applications.

 The main business challenges addressed by this solution include:

• Protect against single points of failure
• Minimize the impact caused by planned and unplanned downtimes
• Reduce the infrastructure complexity and operational costs
• Provide and end-to-end automated resilience model
• Improve the utilization of resources across data centers

To download the entire White Paper, visit - https://community.emc.com/docs/DOC-29575

For more information on Symantec ApplicationHA, visit the product page.

In questo articolo sono elencati numerosi libri in formato elettronico appartenenti a diverse tematiche nell'ambito IT, e che possono essere utili per le normali attività giornaliere da parte degli amministratori di sistema.

Sono presenti manuali IT, ebook ed altri utili documenti per system administrators e tecnici del settore IT. Con la speranza che questi titoli possano essere un valido aiuto per novizi ed esperti, che potranno trovare delle utili informazioni nei diversi ambiti delle tecnologie informatiche.

Nota: questo articolo viene costantemente tenuto aggiornato, inviatemi le Vs segnalazione nel caso vi siano altri interessanti titoli meritevoli di essere aggiunti.

As we have seen in previous articles [1] or download [2] it is now very simple to add Patch Compliance trending to your Symantec Management Platform. 

However the solution provided operates outside of the Symantec Management Console. So we will look at how to integrate the Patch Trending site and graphs into the Management Console, to further simplify management and increase visibility over the patch compliance trends.

In Part I (this article) we'll integrate the full trending site into the Management Console.

In Part II we will integrate the charts into the console right click options, so anytime you right click on a bulletin you can access the current trending charts [3].

Part I: Integrating the Patch trending Site into the Management Console

Here is the starting point: the PatchTrending site is external to the Management Console. So to access it users must know or be given the url.

We will do this integration from the "All Settings > Notification Server > Console > Menus" editor.