I decided to put some search sentences using Google.

Well I found a lot of stuff about this problem, but all the solutions where pointing to the client site. That’s strange because till yesterday all was working well and no windows update is pushed to the clients.

Then a found a blog post about Implicit vs Explicit Document Check-out in Sharepoint from Ian. Reading this and actually looking at the screens. The modified date of the document that could be it. Because in the past, lets say the last time we used visual source save ye ye I know but its a long long time ago. I had a similar issue.

So I opened up the farm SQL server again and have a look at the system date/time. And yes there it is for a unknown reason de SQL server was running 1 hour behind the time of our AD. That’s very strange because of the time sync is managed by AD and al other machines are pointing to our domain server. I have to investigate this so it will not happen again.

So after setting the date/time to the same time as our AD. All the file locking problems are gone with the wind…

So keeping that in mind that its not your sharepoint server which is responsible for the date/time stamps on your documents, but its your SQL server.

Cheers

Open IE and check the connections tab.
Choose LAN settings and check use proxy and check Bypass proxy and choose Advanced.
Put your localhost ip 127.0.0.1 and port number 80 in the boxes.
And check use the same proxy and don’t forget to fill in exceptions ” *.* “

This can also be done by a group policy. Just start the GP editor

Cheers.

First of all
On the machine that has to run the task, create the credentials file:
From the PowerShell command run New-VICredentialStoreItem -host ‘vccenter’ -user ‘marcus’ -password ‘garvey’ -file c:\vc_cred

Getting the credentials:
$creds = Get-VICredentialStoreItem -file c:\vc_cred

so in code it will end up as:

###################################################################
#
# ReverseToSnapshot.ps1
#
# -Get stored credentials
# -Connect to vCenter
# -Shutdown Virtual machine
# -Set to required snapshot
# -Remove other snapshots
# -Start Virtual machine again
#
# Example:
# .\ReverseToSnapshot.ps1 -vmname TIIS01.domain.com -snapshotsname Do-Not-Remove-Default
# Version 1.0 juni 2010 JW Nieuwenhuizen ict.myjewe.nl
#
####################################################################

param(
    [parameter(Mandatory = $true)]
    [string]$vmname,
    [string]$snapshotsname
)

function PowerOff-VM{
    param([string] $vm)
        if((Get-VM $vm).powerstate -eq “PoweredOff”){
        Write-Host “$vm is already powered off”}
        else{
    Shutdown-VMGuest -VM (Get-VM $vm) -Confirm:$false | Out-Null
    Write-Host “Shutdown $vm”
    do {
        $status = (get-VM $vm).PowerState
    }until($status -eq “PoweredOff”)
    }
}

function PowerOn-VM{
    param( [string] $vm)
    if((Get-VM $vm).powerstate -eq “PoweredOn”){
        Write-Host “$vm is already powered on”}
    else{
        Start-VM -VM (Get-VM $vm) -Confirm:$false | Out-Null
        Write-Host “Starting $vm”
        do {
            $status = (Get-vm $vm | Get-View).Guest.ToolsRunningStatus
        }until($status -eq “guestToolsRunning”)
    }
}

function Remove-Snapshot-VM{
    param( [string] $vm, [string] $vm1)
    $snaps = Get-Snapshot -VM (Get-VM -Name $vm)
    foreach ($snappie in $snaps)
    {
        if ($snappie.Name -eq $vm1){
        Write-Host “This one we need again $vm1″}
        else{
        Get-Snapshot -VM (Get-VM -Name $vm) -Name $snappie.Name | Remove-Snapshot -Confirm:$false | Out-Null
        }
    }
}

#######################################################################################
# Main script
#######################################################################################
# Import VimAutomation.Core to run from a “normal” powershell prompt
add-pssnapin VMware.VimAutomation.Core

# Get and Decript credentials and Connect vcenter Using AD credentials
$creds = Get-VICredentialStoreItem -file c:\vc_cred
    foreach ($item in $creds){
    Connect-VIServer -Server $item.Host-User $item.User -Password $item.Password
}

$poweroff = PowerOff-VM $vmname

# Set Snapshot name
$snapname = Get-Snapshot -VM (Get-VM -Name $vmname) -Name $snapshotsname
# Set VM to snapshot
Set-VM -VM $vmname -Snapshot $snapname -confirm:$false

$removesnap = Remove-Snapshot-VM $vmname $snapshotsname
$poweron = PowerOn-VM $vmname

Disconnect-VIServer -Confirm:$False

Thanks to A Fokkema and baars.it and secure-credential-storage

param ($Age = 30)

Connect-VIServer localhost
$vm = Get-VM
$snapshots = Get-Snapshot -VM $vm
Write-Host -ForegroundColor Red “Old snapshots found:”
foreach    ($snap in $snapshots) {
    if ( $snap.Created -lt (Get-Date).AddDays( -$Age )){
        Write-Host “MachineName:” $snap.VM “Name: ” $snap.Name ” Size: ” $snap.SizeMB ” Created: ” $snap.Created
        }
}

Alert: Failed to send notification using server/device
Source: Microsoft.SystemCenter.NotificationServer
Path: pscm01.contoso.com
Last modified by: System
Last modified time: 20-5-2010 17:25:14
Alert description: Notification subsystem failed to send notification using device/server ‘ocs01.contoso.com’ over ‘sip’ protocol to
sip:Domainuser@contoso.com’.Microsoft.Collaboration.OperationTimeoutException: This operation has timed out.: Sip response: 0×0 (0×0). Rule id: Subscription{GUID}
Notification subscription ID generating this message: {GUID}

First off all prepare your communication server

Export your certificate.(complete chain)
Check both entry’s as Front End Server protocol.

The next thing to do is add your SCOM2007R2 server as a authenticated server.

Now it’s time to reboot your Communication server.

Above I mentioned “After the setup of my IM-Channel and subscribers”

Import your certificate into your SCOM2007R2 server (from your communication server) to your personal local machine store , after import check if the path is fully recognized.

Add a new user to your AD (domain user, the name in my case “scom2007r2″, and create a mail and sip address for this account)
On the System Center Operation Manager go to Administration. Click on accounts. Now create a new Run As Account below some details.

Click on Add pscm01.contoso.com as secure server. Ok that’s done now set up a profile, as you can see it’s important to select as association a class rather then a group or object. And of coarse select the run as account. 

Now it’s time to create your Notification Channel:

After this it’s time to setup your subscribers and there Subscription.

Having said this and a reboot of my SCOM2007R2 server. I start receiving messages

Before you can start using it you have to download the OVF Tool from VMware. http://www.vmware.com/downloads After installing the tool add the OVF tool Path to your environment variable. To check if it’s done well open your command line anf type ovftool -h, now the help will be displayed.

The default usage is ovftool <options> <source locator> <target locator> more specific switches and tips can be found in the ovftool_10_userguide.pdf 

If you receive a error while starting “Device ‘cdrom1′ has a backing type that is not supported.” just remove it from your vmx config file. Good luck.

First create a snapshot after the latest changes. After that has been done you can delete the other one’s using the gui or commandline.

To commit the latest one to the original you have to use the commandline.

• vmware-cmd -l   this will display a full list of available vm images (*.vmx) ” /vmfs/volumes/Guid/vmname/vmconfigname.vmx”
• vmware-cmd /vmfs/volumes/Guid/vmname/vmconfigname.vmx hassnapshot
  hassnapshot() = 1  if there no snapshot the result will be 0
• vmware-cmd /vmfs/volumes/Guid/vmname/vmconfigname.vmx removesnapshots
  removesnapshots() = 1 On succesfull removal the ruslt will be 1

That’s it for now

Choose your ntp server internal or external http://www.pool.ntp.org/

Copy and paste it in notepad and save as *.reg file. Merge it into the registry and restart your w32time service.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Parameters]
“Type”=”NTP”
“NtpServer”=”nl.pool.ntp.org,0×1″

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config]
“AnnounceFlags”=dword:00000005

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer]
“Enabled”=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpClient]
“SpecialPollInterval”=dword:00000384

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\Config]
“MaxNegPhaseCorrection”=dword:00000e10
“MaxPosPhaseCorrection”=dword:00000e10

Open the command prompt and type:

net stop w32time

net start w32time

This while version “VMware-converter-4.0.0-146302″ is up and running on vcb proxy server and backupexec server. After searching a lot of google options I found the solution.

It seems that the only working Vmware Converter version is VMware-converter-3.0.2u1-62456.exe.

So I uninstalled the new version 4, and installed the old version 3.0.2 and well believe it or not its running.

Roles: Application server, Webserver(Application server foundation,web server support also IIS6)

Features: .Net Framework 3.0 Features, Group Policy Management,Remote server Administration Tools, Windows Proces Activation Service.

Apply al windows updates.

After that you have to install SQL2005 including reporting and integration services. Installed SQL2005 SP3 and again all Windows updates.

Then another pre-requirement .Net Framework 1.1 and SP1. And again install your windows updates and reboot your machine. If you take a look within the IIS manager Handler Mappings you will discover the ASPNET 1.1 entry’s

Create your “DAS” account on your Active Directory and make local admin on your ForeFront Server.

Mount your iso image or play the CD/DVD “en_forefront_client_security_x86_x64_cd_x13-62435.iso”

And start the install. Give al the information during installation and wait a moment.

If run into a error as “System.Runtime.InteropServices.COMException (0×80080005)” this is mostly a timing issue use the “back button and click next”.  yep it sounds bad but it’s an official workaround.

Other issues can be found http://technet.microsoft.com

And on the end.

Run windows update again! Your ready.

For manual deployment you can use Forefront Client Security Deployment Tool

The Security setting may not correct by the initial setup http://technet.microsoft.com