APP Controller 2012: Cannot connect to SQL

I am installing App Controller to provide Client access to my Lab Private Cloud to students.

On “Configure the SQL Server Database” step the setup stopped for a long time and finally gave me “The specified database has insufficient disk space” message.

I double checked the space and it is ~100GB available

I noted “Instance name” was not populated automatically, so it looked like a firewall issue for me. I checked my Windows firewall and all SQL ports are open (including SQL browser). I added File and Print Sharing and DCOM, but that did not help.

Resolution:

I created a custom firewall rule allowing all traffic from App Controller Server to SQL. The Instance Name field was populated right away and setup continued how it should be.

I did not investigate what exactly port was a root cause of the issue – just implemented a quick resolution for my Lab environment.

Hyper-V: Snapshot all VMs on a host

I am an MCT and sometimes need to prepare a class for training. Microsoft provides Hyper-V – based VMs for that and I need to use snapshots to be able safely recover VMs if a student will go too far

Microsoft recommends to do it one by one from GUI.

I found PowerShell is much better: as soon as all VMs are ready I just run:

Get-VM | CheckPoint-VM –SnapshotName  StartingImage

That makes snapshots on all VMs and names them “StartingImage” (so I do not need to rename them )

Looks like an easy thing, but save a lot of time.

SCCM 2012: Keep your SCCM database clean

Peter wrote a nice script to remove devices deleted from AD from SCCM database. That is what I always recommend to my clients too: keep your AD clean and use it as a primary inventory source.

SCCM 2012: SQL 2012 SP1 is supported

As Microsoft SCCM team announced in its blog (http://blogs.technet.com/b/configmgrteam/archive/2013/02/11/support-announcements-for-february-2013.aspx) SQL 2012 SP1 is supported with some versions of SCCM now. (Note: still not supported with WSUS, so be careful with WSUS DB location )

Here is the matrix:

Important:

1. SQL 2012 SP1 is not supported for SCCM 2012 RTM

2. a CU2 for SQL 2012 SP1 must be installed

3. according Enhansoft blog Reporting Services are supported for SCCM 2012 SP1 even though are not listed in the matrix

Lync 2012: Federation failed with error “SIP/2.0 504 Server time-out”

I recently helped one of our Consultants to troubleshoot a Lync Federation issue.

 

Issue: When a Client tries to add a user from a Federated domain it gets “

When contacting your support team, reference error ID 504 (source ID 239).

Troubleshooting information is available online, including best practices for using Lync.” message.

 

Resolution: Edge Server log shows:

TL_ERROR(TF_CONNECTION) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab3fee (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
LogType: connection
Severity: error
Text: Receive operation on the connection failed
Local-IP: 69.10.XXX.XXX:54814
Peer-IP: 209.205.XXX.XXX:5061
Peer-FQDN: My-Edge-FQDN
Peer-Name: Partner-Edge_FQDN
Connection-ID: 0x13703
Transport: M-TLS
Result-Code: 0x80072746 WSAECONNRESET
Data: fqdn=”Partner-Edge_FQDN“;peer-type=”FederatedPartner”;winsock-code=”10054″
$$end_record

 

TL_ERROR(TF_DIAG) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab4024 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(143))$$begin_record
LogType: diagnostic
Severity: error
Text: Message was not sent because the connection was closed
SIP-Start-Line: SUBSCRIBE sip:username@Partner-DOMAIN SIP/2.0
SIP-Call-ID: 495169bf05e041e39222905f46236f31
SIP-CSeq: 1 SUBSCRIBE
Peer: Partner-Edge_FQDN:5061
$$end_record

TL_INFO(TF_PROTOCOL) [1]1828.1FFC::02/07/2013-19:19:35.910.00ab4333 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 1484110210
Instance-Id: 0000567F
Direction: outgoing;source=”local”;destination=”internal edge”
<Private information here >

CSeq: 1 SUBSCRIBE
Call-ID: 495169bf05e041e39222905f46236f31
Via: SIP/2.0/TLS 10.10.XXX.XXX:59199;branch=z9hG4bK9558ABE4.49ED0FF1C7027493;branched=FALSE;ms-received-port=59199;ms-received-cid=600
Via: SIP/2.0/TLS 192.168.XXX.XXX:54768;branch=z9hG4bK54197F18.D4F20C41F31B0497;branched=FALSE;ms-received-port=54768;ms-received-cid=33DD500
Via: SIP/2.0/TLS 192.168.XXX.XXX:65137;received=99.228.XXX.XXX;ms-received-port=65137;ms-received-cid=12800
ms-diagnostics: 1047;reason=”Failed to complete TLS negotiation with a federated peer server”;WinsockFailureCode=”10054(WSAECONNRESET)”;WinsockFailureDescription=”The peer forced closure of the connection”;Peer=”Partner-Edge_FQDN“;Port=”5061″;source=”My-Edge-FQDN“
Server: RTC/4.0
Content-Length: 0
ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=My-Edge-Internal-FQDN;ms-source-verified-user=verified
Message-Body: –
$$end_record

Even though we are using Entrust certificate on our Edge the Partner’s Edge does not trust it!

I sent our Entrust certificate chain to Partner to install on Edge and it fixed the issue.