Protection agent cannot be installed on machine where dpm is installed DPM 2012 SP1 Agent Error

When you install/update your DPM 2012 protection agent from pre SP1 or SP1 to SP1 RU1 through DPM console it’s fairly easy. You just have to click on Update available in Management/Agent tab and the job is done. 

Sometimes (Firewall, incompatible version, etc.) DPM agent cannot be updated from DPM console and you need to proceed manually.
When you try to do manual install/update, it’s a little bit more tricky 🙂 Because there are two DPM “agent” folders in DPM directory structure:
..\DPM\ProtectionAgents\RA\4.1.3313.0\… => Which contains agent SP1 RTM
..\DPM\agents\RA\4.1.3322.0\… => Which contains agent upgrade for SP1 RU1
To manually install/Update DPM agent to DPM 2012 SP1 RU1 you have to: 

  1. Uninstall old agent from control panel
  2. Manually install agent SP1 RTM – 4.1.3313.0
  3. Manually apply upgrade SP1 RU1 – 4.1.3322.0

# Install/upgrade process could be done with a sample Dos script:

Net use U: \\DPMName\c$
Cd /d “U:\Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\4.1.3313.0\amd64″
DPMAgentInstaller_x64 /q /IAcceptEULA
:: Let enough time for install 
ping 127.0.0.1 -n 240
Cd /d “U:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3322.0\amd64\1033″
DPMAgentInstaller_KB2791508_AMD64 /q
:: Let enough time for install
ping 127.0.0.1 -n 240

:: in case of new installation, just remember to attach your new protected server to your DPM Server.
cd /d “C:\Program Files\Microsoft Data Protection Manager\DPM\bin”
setdpmserver.exe -dpmservername DPMName
Net use U: /delete

 

 

http://yetanotherdpmblog.blogspot.fr/

Remove domain sender permissions Exchange 2010

One of the more annoying types of spam is the one that seems to be coming from your own domain; or worse— from your own email address! Of course, users from your own domain don’t generally spam each other— unless you’re using one of the free web-based email services. And most of us don’t spam ourselves.

Obviously, this is coming from a spammer who has spoofed your email address, or that of someone else from your domain. Unfortunately, SMTP— the protocol that allows mail clients and servers to exchange email, allows headers to be spoofed easily.

Thanks to the extensive Transport Permissions model in Exchange 2010, we can easily prevent such spam. Receive Connectors have the ms-exch-smtp-accept-authoritative-domain-sender permission which dictates whether an Accepted Domain can be used in the MAIL orFROM headers. External/internet hosts submit mail to your server without authentication, as anonymous senders. To prevent anonymous senders from sending mail using your domain(s), we need to remove the ms-exch-smtp-accept-authoritative-domain-senderpermission assigned to them.

Use the following command to remove the ms-exch-smtp-accept-authoritative-domain-sender permission from NT Authority\Anonymous Logon on internet-facing Receive Connector(s):

Get-ReceiveConnector “My Internet ReceiveConnector” | Get-ADPermission -user “NT AUTHORITY\Anonymous Logon” | where {$_.ExtendedRights -like “ms-exch-smtp-accept-authoritative-domain-sender”} | Remove-ADPermission

Once this permission is removed, when anonymous senders try to submit mail using your Accepted Domain(s).

You can try to send a fake mail by using this site: http://emkei.cz/

 

 

Outlook2010 Profile Roaming with Folder Redirection

Ok, i got it to work now with two scripts:

One that activates when user login:

cmd /c regedit /C /S %appdata%\Outlook_Profile.reg
cmd /c regedit /C /S %appdata%\Office_Setup.reg

And one that activates when the user logs off:

cmd /c regedit /E %Appdata%\Outlook_data\Outlook_Profile.reg “HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\%username%”
cmd /c regedit /E %Appdata%\Outlook_data\Office_Setup.reg “HKEY_CURRENT_USER\Software\Microsoft\Office”

This exports and imports the regfiles of the outlook settings. So that the users settings follows with the user, regardless of what computer they log in to.

SCCM2012: When will SCCM2012 be supported with SQL 2012 and Server 2012? And when are the releases?

Here are som facts about releases:

 

Windows 8

Volume Licensing  and available to partners – 16 August

RTM – 26 October

Windows Server 2012

Volume Licensing and available to partners – not announced “We will also make the software available to our volume licensing customers in the next couple of weeks.”

RTM – 4 September

SQL Server 2012

RTM – 6 Mars

SCCM 2012 SP1

Sccm2012 with support for Windows 8 OSD and Server2012

CTP2 Released Today 15 August

 

So it seems at the latest we will get to work with all of these combined is the 4 september, depending on the SP1 for CM12.

Microsoft: DPM2010, troubleshooting errors

System Center Data Protection Manager (DPM) 2010 is a server-based application that enables disk-based and tape-based data protection and recovery for computers in and across Active Directory domains. DPM performs replication, synchronization, and recovery point creation to provide reliable protection and rapid recovery of data both by system administrators and by end-users. DPM uses replication, the Volume Shadow Copy Service (VSS) infrastructure, and a policy-driven engine to provide businesses of all sizes with nearly continuous protection and rapid, reliable data recovery.

Troubleshooting:

There are three types of errors that i have bumped in to those are the following:

  • Replica is inconsistent
  • Recovery point creation failed
  • Unable to configure protection

All of these errors generates a critical alarm in the monitoring tab. They are in fact very critical since it could mean no backup at all involving the affected server/client. But do not panic, they are in fact easy to get to working again. All you have to do is follow my steps in this troubleshooting-guide. This is an example of how it could look:

Replica is inconsistent

This alert is generated when the replica of the specified volume on the DPM server is inconsistent with the data source. All protection activities for the data source will fail until the replica is made consistent with the data source by performing synchronization with consistency check.

Possible causes for an inconsistent replica include:

  • The consistency check that DPM automatically performs on a newly created replica during replica creation has not yet been performed.
  • The synchronization log on the file server ran out of space before all data changes to the data source were logged.
  • DPM determined that the file server shut down unexpectedly.

If a daily consistency check is scheduled, DPM will automatically perform the consistency check at the next scheduled time.

Recovery point creation failed

This alert is generated when DPM fails to create a recovery point for a data source. Data Protection Manager (DPM) creates recovery points for each data source from which you can recover data.

The error conditions and recommended actions associated with each “Recovery point creation failed” alert are provided in the alert details for the DPM alert. Follow the recommended action in the alert, and retry the job. You can access the recovery points on the DPM server to recover previous versions of data. You can manually create a recovery point in the protection task area.

Unable to configure protection

DPM periodically contacts the DPM agents to check connectivity status. This alert is generated when the DPM server has not been able to contact the specified file server since the specified time. If the connection is not established, subsequent data protection jobs will fail. The error conditions and recommended action associated with each connection failure are provided with the alert. Some common causes include:

  • File server is not available, The file server has been shut down or has been disconnected from the network and cannot be contacted.
  • The DPM File Agent is not compatible with DPM software, A more recent version of Data Protection Manager has been installed on the DPM server, but the DPM File Agent on the file server has not been not updated.
  • File server is behind a firewall
  • Firewall settings on the DPM server or the file server are preventing the DPM server from communicating with the file server.

1. Make sure the clients agent is reachable and working correctly navigate Management > Agents > Refresh

2. On the clientserver start CMD in administrator mode. Navigate to C:\Program Files\Microsoft Data Protection Manager\DPM\BIN enter following:

 SetDpmServer.exe -DPMServerName DPMSERVER.yourdomain.com

3. If it’s a server that is not on the same domain as the DPM server use this instead:

SetDpmServer.exe -DPMServerName adm-sto-vsh-10.admin -isNonDomainServer -userName “LocalWindowsaccount” -productionserverdnssuffix “Domain”.yourdomain.com

It will promt you for the password, enter the password and configuration will complete successfully.

4. Restart the server

5. Preform  the  consistency check manually again. And we should be done.

6. If this did not help, uninstall the client agent and install it again. And repeat phase 2 + 3.

 

//Karl

Microsoft: Reduce Sharepoint Datase Log file (WSS_Content_log.LDF)

SharePoint Config database logs are one thing to keep an eye on since they do have a tendency to grow. If you don’t perform a full farm backup usually the log doesn’t get emptied and it just keeps bloating.

If you’re running SQL Server Express with default installation, you can find the files in C:Program Files\Microsoft SQL Server\MSSQL.1MSSQLData

As we see in the example above, even though the database is only 9 gig, the log file grew to 34 gigs. Let’s reduce that:

1. If you don’t have it yet, download and install SQL Server Management Studio express from here.

2. Run the Management Studio and connect to your SQL Server.

3. Expand “Databases” and select your config database “SharePoint_Config”.

4. Right Click it, select Tasks –> Shrink –> Files

5. In the new window select Release unused space and click OK.