Archive
Resolving Amazon Echo registration error 10:2:5:60:1
When trying to register a new “Amazon Echo” into my home network, I received the following error:
“There was an error registering your device. Visit Help for troubleshooting tips. Error 10:2:5:60:1”
I followed all of the usual steps (reset device, reset router, uninstall/reinstall mobile app, etc.), but nothing worked. I also setup a second Wi-Fi network to see if that was the issue.
I should point out that I already had another working Amazon Echo Dot device that was previously setup and still working on the same WiFi network that didn’t have any issues registering. I also took that offline to ensure that wasn’t an issue.
I then removed all other WiFi devices from the network. It still didn’t work.
I called Amazon support. They were great, but it still didn’t work. So they sent me a new one and received it in two days. They’re awesome.
What wasn’t awesome was that the new device had the SAME ERROR! So now I know it IS the network.
What I found was that with all devices off of the network, I check the logs (Advanced > Logs) on my Cable Modem device (Netgear c6300, Firmware V2.01.14) that I saw that the device was reporting a DoS attack that were coming from the Echo device. Below is the error I saw:
[DoS attack] Port Scan PROTO:UDP SPT:50395 DPT:123
The firewall didn’t have any restrictions on the devices that could be on the network, nor blocking outbound traffic, so this was weird. I found a setting to ignore this type of traffic and not block it. I crossed my fingers and gave it a try.
First, login to your device (typically http://192.168.0.1/ ), then click on the “Advanced” tab. Click “Setup” in the left menu, then click on “WAN Setup”. Enable the Checkbox for, “Disable Port Scan and DoS Protection”, then click “Apply”.
Once your device has reset, then go through the normal setup process using Amazon Echo. Now your Echo should be working. After it’s working, go back into your Netgear setting and disable the setting we applied earlier. Afterward, the Echo should still work AND you’re protected from Port Scan and DoS protection.
I hope this helps you in your situation.
To Zune or to Spotify… That’s the question
When I heard that Spotify was coming to the United States I thought, “What’s the big deal”? With such a question in hand, I when to the site to get notified when the service was available. I was lucky enough to get approved for early access only a few days later. After using the free version of the service, I quickly saw how it could be a game changer.
First off, I’ll point out that I’ve been using the Microsoft Zune services since it came out. Full Disclosure: I worked for Microsoft at the time Zune came out. Regardless, it’s a quality product.
To keep this post short, I’ll get to the basics.
Zune Pass: http://zune.net
- User Interface is easy and beautiful.
- Great integration with Windows Phone (I have a test phone and it works like a charm), XBOX 360, PC, and Zune HD (cool but limited device)
- Each month I get to keep 10 songs via MP3, everything else is protected (WMA format) but as long as I keep paying the subscription I can get as much as I want.
Spotify: http://www.spotify.com
- Free version allows for (free) streaming of music. (Awesome)
- Paid versions allow access via you mobile device. I have an iPhone and it’s pretty nice. It also works on other mobile platforms such as Windows Phone and Android.
- Streaming is super fast.
Winner: To be determined, but right now I’m starting to think I’ll go the way of Spotfiy unless Zune makes a few changes. If Spotify can get away with the free service, why can’t Zune? Plus I like being able to keep 10 songs via MP3 each month.
Virtual Desktops and Federal Desktop Core Configuration (FDCC)
A few years ago the United States Federal Government, specifically the U.S. Office of Management and Budget) created a PC standard for then entire government to follow. The provided over 300 settings for Windows XP and Windows Vista in order to create a standard for all computers. This is what is now knows as Federal Desktop Core Configuration (FDDC). There is a ton of resources on the Internet, mostly on the .gov sites, that provides guidance on what these settings are and how to audit those settings using publicly available tools.
As with any IT Department, defining the policy is one major leap. But to some degree, that’s the easy part. Now you must deploy that configuration and ensure it stays enforced, not to mention audited and reported on. With the U.S Government, having a mandate from the OMB is pretty powerful, thus making this problem space even more critical.
The FDCC is a perfect fit for Virtual Desktops from a deployment and management perspective. Virtual Desktops is all about OS and Application standardization and consistency. Thinking of having a pool of available OS instances, just waiting for a user to login from a remote device which could be a hardened thin-client or legacy PC. All of those OS instances are based on a “Master Image” that has been fully configured with the FDCC policies. When a user logs in, all of their applications are delivered via “Application Virtualization” (e.g. Microsoft App-V or Citrix XenApp) which is still abstracted from the underlying “Master Image”, thus keeping the desktop within FDCC standards. All of the users data and application data is stored on a centralized store (e.g. SAN) which again keeps the “Master Image” clean of user data and provides additional benefits for the user and IT (e.g. daily backups of all user data).
So what about those users that go on the road? Well this is where Virtual Desktop is still in play. Using Microsoft MED-V or Citrix XenDesktop, a user can still take their FDCC approved image and applications on the road with them. The bonus about Virtual Desktop deployments is that the process and image based deployments can be done directly on a physical machine as well. You just take that master image, settings, and even application virtualization and deploy it directly on a laptop. Using something like Microsoft System Center Configuration Manager and the Microsoft Deployment Toolkit (a solution accelerator) delivers this type of deployment scenario for both virtual and physical deployments.
Just like in any Virtual Desktop deployment, it’s not like Server Virtualization! Managing the deployment and operations for a Virtual Desktop Infrastructure (VDI) is extremely different and requires lots of up front planning. Not to say that Server Virtualization doesn’t, but when you consider the number of different users actually logging onto those Virtual Desktops, there are lots of end user scenarios you have to think through. Even with the guidance of the OMB for FDCC (see, here comes the acronym soup), you may still define additional policies for given user roles. Which could include access to applications via a variety of delivery models (e.g. web applications, application virtualization, etc.)
ISV Guidelines for Hosted Microsoft Dynamics CRM 4.0 Part 1
ISV Guidelines for Hosted Microsoft Dynamics CRM 4.0 Part 1
The intent of this series of blogs is to provide a basic guideline for Service Providers looking to offer CRM as a target platform for ISV’s looking to deploy their application on the Internet as a Software as a Service (SaaS) model. It’s also a guide for ISV’s to understand that the design decisions they make during development will have a profound impact on their available hosting with regards to deployment architectures and pricing.
- Part 1: Introduction
- Part 2: CRM as an Application or Platform
- Part 3: Shared or Virtualization Deployment & Licensing
- Part 4: Provisioning & Control Panels
- Part 5: Making the Leap
Introduction
With the release of Microsoft Dynamics CRM 4.0 (MSCRM4), Microsoft has provided not only a great CRM application, but also a business application platform. There are many software vendors and consulting organizations that have already leveraged MSCRM4 in the traditional deployment where the application or solution is installed locally on a customers server. This scenario is typically called “On-Premise”. While this deployment model works great for some customers, many business departments are looking to gain access to applications that improve their business, but without the hassle and cost of deployment and operations within their IT department. It’s not that an IT department can’t handle new applications, but it takes time, money, and knowledge to add a new application into the business. Business applications that are hosted on the Internet and accessible via a traditional browser is known as “Software as a Service” (SaaS). The business world is all abuzz about SaaS and it’s potential impact to deliver rich applications to departments, on-demand, with a monthly fee, and without the need for upfront deployment or hardware costs. Sounds Great, right? Well for some scenarios it is pretty great, but there are a number of other reasons why this might not be so hot (e.g. Security, Internet Outage, Performance, End User Training, etc.).
Here are some examples of where the SaaS deployment model is so interesting for many customers:
- Trial – Your software may be great and the value is high, but how will the customer know if they can’t try it in all it’s glory? Sure they could download the software and use it, but not it requires hardware, time, and the knowledge to get it installed and configured. With the SaaS based model, they can get access to your application instantly! Even if they are interested in an on-premise deployment, they can at least get the feel for it right away which will help with their buying decision.
- Temporary Usage – Some customers may decide that they do want the on-premise version. This could be for any number of reasons the customer may have or because your on-premise version has more capabilities (e.g. integration with a VOIP solution, devices, etc.) than the SaaS version. In this scenario, the customer goes beyond the trial online and wants to continue to use it. Let’s say it’s going to take six months for the customers IT team to purchase, deploy, and operationalize [killing the English language] an environment for the on-premise version. So until then, the customer uses the SaaS version. This gives the customer some flexibility in their deployment, instant access to the application which will improve their business, and increases your sales and revenue.
- Migrations – I’m sure you’d seen a number of customers that would LOVE to go to a new version of a software application they’ve been using, but the time and cost to upgrade hardware, update the data, and learn the new platform is just too much for them. This is another great scenarios for SaaS to meet the business needs of the customer, removing the strain on their IT department, and increasing revenue for you (SaaS Vendor).
- SaaS Everything – There is a growing trend for many organizations to outsource more and more of their applications. Well, that’s what the industry says at least. For those businesses, you at least need to have SaaS as a delivery option for them or you may lose some business.
There are a number of Service Providers out there today that are offering hosted solutions for Microsoft Exchange Server (for consumer and business mail), Windows Server (for web hosting with Internet Information Server which is part of Windows Server), SQL Server (for databases), and SharePoint Services (for document and information collaboration). MSCRM4 is a natural extension for Service Providers to also offer this service. While there is much competition in the space of CRM systems on the Internet, including the current leader Salesforce.com, MSCRM4 is easily configurable, extensible, and leverages the Microsoft .NET Framework which will enable the army of Microsoft developers hooked on their Microsoft Visual Studio development environment to build rich business applications.
When developing software, the sky is the limit! Especially when developing on the Microsoft platform and technologies, but you must be careful that you follow some basic guidelines to ensure your application can be hosted as a SaaS application and meet your target business objectives. There is much to consider and I hope you find the rest of this series helpful.
Note: If there are specific areas you’d like me to cover in future posts, please post a comment below.
Conrad Agramont 