Djoey.Net

Lync 2010 Installation with backend SQL Cluster failed login

Tue, 27 Sep 2011 09:03:48 +0000

I started installing Lync into our production environment after having installed it on a test lab, the only thing that differs was in production we use a SQL cluster as backend. In the test lab I have used a single SQL cluster server as backend.

I created a topology and tried to publish it, it immediately threw me an error with failed login for user DOMAINAdministrator. After searching for some answers via Google which as always led my in the wrong direction thinking it actually was an error on my SQL cluster.

The only thing you need to double check is that on all nodes the virtual sql instance you have opened the SQL Browsing Service (UDP port 1434 by default) and allow for remote administration in the local firewall and all other firewall that might be in between.

Continuing the search on Technet reading about Configuring SQL Clusters in the Lync Deployment pages I found the correct powershell commands to use:

Install-CSDatabase -CentralManagementDatabase -SqlServerFqdn sqlfqdn.mydomain.tld -SqlInstanceName mysqlinstancename

Now i got somewhere, still getting an error but this time it made more sense: error_no_db_drive_access

This seemed to me that somehow Lync was trying to setup the database files and logfiles for the SQL instance on non clustered disks and i decided to alter my powershell command with:

Install-CSDatabase -CentralManagementDatabase -SqlServerFqdn sqlfqdn.mydomain.tld -SqlInstanceName mysqlinstancename -DatabasePaths X:lyncdatabaselogs,Y:lyncdatabase

And Halleluja! it created the CentralManagementDatabase! After that I continued to publish the topology. And for the other SQL Databases that needed to be created I choose the advanced button and instead of "Automatically determine database location" I selected: "Use SQL Server instance defaults".

Testing URL Shortener

Wed, 15 Jun 2011 18:35:04 +0000

I have put in place a URL shortener specifically for my website, it should automatically post this with the correct url shortener to twitter.

Synology ds710+ pxe server with ping and dd-wrt

Tue, 14 Jun 2011 08:56:09 +0000

This weekend I decided to put in place image capture and restore functionality in my network using all the pieces of hardware i already owned. Reason is that I do not like it when re-installing Windows I have to do updates etc nowadays you'll lose an entire day re-installing. For imaging I use ping. Alternatively I will see if I can add unattended in the pxe menu and rollout unattended install's of my OS's. Will blog about that later.

I will write down the steps I have taken to achieve my goal:

1.
Enable the Command Line Interface of your Synology (steps may vary with different DSM Versions)

2.
We need to logon the Synology using ssh or telnet (depens on which you have chosen in the previous step), you can download PuTTY for this task. Login as user "root" and give the password you have setup for the admin user.

3.
Next we need the ipkg package system, the package you need to download is dependent on the processor architecture your Synology is using. You can find out here (German warning). Switch to the ssh or telnet session you have opened in putty. and use the following commands to download and install the ipkg installer:

nas> wget http://ipkg.nslu2-linux.org/feeds/optware/syno-i686/cross/unstable/syno-i686-bootstrap_1.2-7_i686.xsh nas> chmod +x ./syno-i686-bootstrap_1.2-7_i686.xsh nas> ./syno-i686-bootstrap_1.2-7_i686.xsh nas> rm -f syno-i686-bootstrap_1.2-7_i686.xsh nas> ipkg update

4.
Now we are going to install the necessary tftp server on the Synology nas

nas> ipkg install tftp-hpa

5.
We need to configure the tftp server. First we make the necessary directories:

mkdir /opt/tftpboot mkdir /opt/tftpboot/pxelinux.cfg (yes this is a directory including a .)

Then we need to check if /opt/etc/xinetd.conf contains the right information you can use the command:

nas> more /opt/etc/xinetd.conf
defaults
{
        only_from      = localhost 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16
        instances      = 60
        log_type       = SYSLOG authpriv info
        log_on_success = HOST PID
        log_on_failure = HOST
        cps            = 25 30
}

You can change the only_from range to tighten security.
If it exists /opt/etc/xinetd.d/tftp check for the following contents:

service tftp
{
       flags            = REUSE
       socket_type      = dgram
       protocol         = udp
       instances        = 30
       wait             = yes
       user             = root
       server           = /opt/sbin/in.tftpd
       server_args        = -s /opt/tftpboot
       cps                = 100 2
       log_on_success   = HOST PID
       log_on_failure   = HOST
       disable          = no
}

6.
Pxe is a small bootloader which is used as secondary bootloader for network boots. You have to place the pxe executable in "/opt/tftpboot". In this case we are configuring ping. You need to download the iso to your PC, extract it and then place it on the nas in one of the shared folders. After you have unpacked the iso and placed it on the nas you can reach it from the commandline. In my case I had to change directory to /volume1/Data/PING-3.01/ You need to move the following 3 files to /opt/tftpboot:

kernel
initrd.gz
pxelinux.0

You can use the cp command to copy the files to the new location:

cp kernel /opt/tftpboot
cp initrd.gz /opt/tftpboot
cp pxelinux.0 /opt/tftpboot

Now you need to create a new file named default in /opt/tftpboot/pxelinux.cfg/default
If you are familiar with vi you can use:

vi /opt/tftpboot/pxelinux.cfg/default

Otherwise it might be wise to first install nano using ipkg: "ipkg install nano" en then use:

nano /opt/tftpboot/pxelinux.cfg/default

copy in the following contents:

DEFAULT rescue
PROMPT 0
LABEL rescue
KERNEL kernel
APPEND vga=normal devfs=nomount pxe ramdisk_size=33000 load_ramdisk=1 init=/linuxrc prompt_ramdisk=0 initrd=initrd.gz root=/dev/ram0 rw noacpi noapm pci=noacpi lba acpi=off apm=off

and save the default file.

That is it for the pxe part.

7.
Now you have to prepare a folder with the partimage structure on the nas.
You can create a newly shared folder with our without password restrictions or use a subdirectory of an existing shared folder.

In my case I used the existing Data share and put in a new folder named LaptopBackup.
You need to download the following zipfile PartImage extract the PartImage folder and its subdirectory's and place it on the newly created shared folder or subdirectory of an existing share on your nas.

8.
One final thing needs to be configured. You need to setup your dhcp server to point to the pxelinux.0 boot file otherwise your computer will not know where to boot from the network. In my case I use a dd-wrt box as my router/ firewall / dhcp server.

Login to your dd-wrt box en in the menu open up the Services. in the submenu open Services again. Do not touch the dhcp options in this screen only alter the DNSMasq option. Fill in:

dhcp-boot=pxelinux.0,nameofyournas,ipofyounas

As an example:

If you are using anything else as your dhcp server you have to consult your manual on how to add the dhcp option. As an alternative you can configure your Synology as a DHCP server

9.
Now you can follow the ping documentation on how to make and restore an image. I have succesfully created an image of all my partitions. I will test the restore functionality asap and report back.

Remove Missing or Failed status VM's in SCVMM

Fri, 27 Aug 2010 08:40:44 +0000

Sometimes when SCVMM F***s up and you are left with double entries of VM's seperated over your cluster one is OK and the other Failed or Missing. Here is what to do:

1. Close the VMM Administrator Console
2. Stop the Windows service named VMMService on the VMM server. (net stop VMMService in a command prompt)
3. Make sure you have the Microsoft Management studio express installed on the same computer on which the VMM Database is and backup your SCVMM DB first !!!! (SQLFQDNMICROSOFT$VMM$) Or enable remote connections in the surface manager first and then connect from another machine with Management Studio express to the SQLFQDNMICROSOFT$VMM$ instance
4. Open SQL Server Management Studio Express, select the VMM database, and then run the following SQL Server script. This should delete all missing virtual machines with a status of Missing from the VMM database. If the script was successful, you will see the following output: Commands(s) completed successfully.
5. When you have tried to repair or delete a VM with the status of Missing in the Admin Console it changes to the status Failed. Now change the number [ObjectState] = 220 in the SQL script into [ObjectState] = 107 and rerun the script.
6. After the SQL Server script has completed, restart the VMMService and open the VMM Administrator Console to verify that the missing virtual machines are now deleted.

BEGIN TRANSACTION T1 DECLARE custom_cursor CURSOR FOR SELECT ObjectId from dbo.tbl_WLC_VObject WHERE [ObjectState] = 220 DECLARE @ObjectId uniqueidentifier OPEN custom_cursor FETCH NEXT FROM custom_cursor INTO @ObjectId WHILE(@@fetch_status = 0) BEGIN DECLARE vdrive_cursor CURSOR FOR SELECT VDriveId, VHDId, ISOId from dbo.tbl_WLC_VDrive WHERE ParentId = @ObjectId DECLARE @VDriveId uniqueidentifier DECLARE @VHDId uniqueidentifier DECLARE @ISOId uniqueidentifier OPEN vdrive_cursor FETCH NEXT FROM vdrive_cursor INTO @VDriveId, @VHDId, @ISOId WHILE(@@fetch_status = 0) BEGIN DELETE FROM dbo.tbl_WLC_VDrive WHERE VDriveId = @VDriveId if(@VHDId is NOT NULL) BEGIN DELETE FROM dbo.tbl_WLC_VHD WHERE VHDId = @VHDId DELETE FROM dbo.tbl_WLC_PhysicalObject WHERE PhysicalObjectId = @VHDId END if(@ISOId is NOT NULL) BEGIN DELETE FROM dbo.tbl_WLC_ISO WHERE ISOId = @ISOId DELETE FROM dbo.tbl_WLC_PhysicalObject WHERE PhysicalObjectId = @ISOId END FETCH NEXT FROM vdrive_cursor INTO @VDriveId, @VHDId, @ISOId END CLOSE vdrive_cursor DEALLOCATE vdrive_cursor ----------------- DECLARE floppy_cursor CURSOR FOR SELECT VFDId, vFloppyId from dbo.tbl_WLC_VFloppy WHERE HWProfileId = @ObjectId DECLARE @vFloppyId uniqueidentifier DECLARE @vfdId uniqueidentifier OPEN floppy_cursor FETCH NEXT FROM floppy_cursor INTO @vfdId, @vFloppyId WHILE(@@fetch_status = 0) BEGIN DELETE FROM dbo.tbl_WLC_VFloppy WHERE VFloppyId = @vFloppyId if(@vfdid is NOT NULL) BEGIN DELETE FROM dbo.tbl_WLC_VFD WHERE VFDId = @vfdId DELETE FROM dbo.tbl_WLC_PhysicalObject WHERE PhysicalObjectId = @vfdId END FETCH NEXT FROM floppy_cursor INTO @vfdId, @vFloppyId END CLOSE floppy_cursor DEALLOCATE floppy_cursor ---------------- DECLARE checkpoint_cursor CURSOR FOR SELECT VMCheckpointId from dbo.tbl_WLC_VMCheckpoint WHERE VMId = @ObjectId DECLARE @vmCheckpointId uniqueidentifier OPEN checkpoint_cursor FETCH NEXT FROM checkpoint_cursor INTO @vmCheckpointId WHILE(@@fetch_status = 0) BEGIN DELETE FROM dbo.tbl_WLC_VMCheckpointRelation WHERE VMCheckpointId = @vmCheckpointId FETCH NEXT FROM checkpoint_cursor INTO @vmCheckpointId END CLOSE checkpoint_cursor DEALLOCATE checkpoint_cursor ------------------------- ---------Clean checkpoint DELETE FROM dbo.tbl_WLC_VMCheckpoint WHERE VMId = @ObjectID exec [dbo].[prc_VMMigration_Delete_VMInfoAndLUNMappings] @ObjectId DECLARE @RefreshId uniqueidentifier exec [dbo].[prc_RR_Refresher_Delete] @ObjectId, @RefreshId DELETE FROM dbo.tbl_WLC_VAdapter WHERE HWProfileId = @ObjectId DELETE FROM dbo.tbl_WLC_VNetworkAdapter WHERE HWProfileId = @ObjectId DELETE FROM dbo.tbl_WLC_VCOMPort WHERE HWProfileId = @ObjectId DELETE FROM dbo.tbl_WLC_HWProfile WHERE HWProfileId = @ObjectId DELETE FROM dbo.tbl_WLC_VMInstance WHERE VMInstanceId = @ObjectId DELETE FROM dbo.tbl_WLC_VObject WHERE ObjectId = @ObjectId FETCH NEXT FROM custom_cursor INTO @ObjectId END CLOSE custom_cursor DEALLOCATE custom_cursor COMMIT TRANSACTION T1

* Source http://technet.microsoft.com/en-us/library/ff641854.aspx

Our daughter Yinthe Milou is born

Fri, 06 Aug 2010 20:54:00 +0000

Our daughter Yinthe Milou is born check Onskind.com for the pictures.