FYI, I seem to have to run a calendar repair on my physician's calendars at least yearly if not more often. Their calendars are changing constantly, I mean like dozens of times a day. The biggest issues we have are when an appointment is moved from one time to another time or day (something else that happens all the time).

We found that completely deleting the old appointment and creating a brand new one on the new time/date completely solves that specific problem - sadly our turn over is high and the new staff aren't told this until there is a problem.

I ran that with my domain admin account. If i use an account that is [email protected], I get the following (that account was used for a long time, and has the highest network credentials by far):

Additional Details

Exception details:
Message: Invalid Uri: parsing problem (no viable alternative): <
Parameter name: value
Type: System.ArgumentException
Stack trace:

Server stack trace:
at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)
at Microsoft.Rtc.Signaling.RealTimeAddress..ctor(String uri)
at Microsoft.Exchange.Tools.ExRca.Lync.TestOcsCore.DoMRASServiceRequest()
at Microsoft.Exchange.Tools.ExRca.Lync.TestOcsCore.Initialize()
at Microsoft.Exchange.Tools.ExRca.Lync.OcsSignInTest.PerformTestReally()
at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformTest()
at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformChildren()
at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformTest()
at Microsoft.Exchange.Tools.ExRca.Tests.TopLevelTest.PerformTest()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at Microsoft.Exchange.Tools.ExRca.Website.PerformTestAsyncDelegate.EndInvoke(IAsyncResult result)
at Microsoft.Exchange.Tools.ExRca.Website.TestExecutionManager.<>c__DisplayClass8.<TestCompleted>b__6()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)
at Microsoft.Exchange.Tools.ExRca.Website.TestExecutionManager.TestCompleted(IAsyncResult asyncResult)
Exception details:
Message: Invalid Uri: parsing problem (no viable alternative): <
Type: Microsoft.Rtc.Internal.Sip.SipException
Stack trace:
at Microsoft.Rtc.Internal.Sip.SipUri.ParseUriString()
at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)

@scottalanmiller That would be nice. I'll hold my breath.

@BBigford said:

It was indeed the firewall. Simple enough I guess... thanks for the quick reply, Scott. Man, I'm glad you brought me over to Mango. Super fast responses.

Woot!!

@BBigford said:

I've been looking for the GUID entries in SCCM 2012 but have been unable to find them. When a machine is reimaged by SCCM, I was under the impression that it does indeed log the machines entry in SCCM. Google has evaded me... do you know where they get stored at in 2012?

2012 is different to 2007 in that you don't need to go hunting for the GUID unless you are digging through the database.

That being said...

If you go to Assets and Compliance --> Overview --> Devices, you can add the GUID column by right clicking any of the column titles and selecting ID. Deleting the device from here also deletes it from the database.

Could not resist....

a9P4OAZ_460s_v2.jpg

To add some on topic input. Last year I ported 50 lines from TDS Telecom ($25k/year for hosted PBX with metered use) and it took almost three months to port all of our numbers. In the end we ended up being unable to port some, namely ones that had been previously ported from Vonage to TDS. Now we run FreePBX in house with all Polycom IP450 (found a lot of them going for $35 each) and spend far less than that.

My point here is, even if you get approval to move forward, and for the political reasons outlined above I wouldn't poke the bear, it will likely be an uphill battle with TDS.

@JaredBusch said:

@scottalanmiller said:

I find pagination works better even on full devices.

I prefer the infinite scroll as long as it works right. It mostly works well on here.

I prefer it when it works too 🙂

Yeah, you can get that to be pretty simple with a little work (and keys.)

Got it solved. I started pointing them at a new server (basically starting from scratch). Still got some inconsistencies but that was resolved by toggling the agent to the new server (after I already pointed it at it). Then I fixed the last couple with a disk allocation mod. What a mind-blowing, super frustrating piece of software.