I saw that Microsoft is closing their retail stores because it “isn’t working out for them”.
In my opinion Microsoft simply didn’t have “enough” stores to compete.
List of Microsoft Retail Store locations:
And a list of Apple Retail Store Locations:
As you will see one has more and one has less.
Both Apple and Microsoft don’t allow for franchising either.
If Microsoft wanted to compete in the retail market they could allow franchising.
Also, Microsoft’s “strategy” is opening next to Apple Stores.
Why not, I don’t know…sell to areas that Apple doesn’t already have a foothold in the retail market?
Reminds me of the quality of internet in Rural areas. There’s big $$$ to be gained there but the profit margin is expected to diminish the further away from a less populated area. Give some one 1 gigabit internet that’s been dealing with 1.5 Mbps and see how many people switch carriers.
Completely open areas for opportunities to profit but no. The plan they thought would work didn’t so let’s just go back to online-only.
Personally, I would be happy to see a Microsoft Reseller Certification option.
Just a quick view at the types of configurations that you might consider depending on your budget and the scale of your infrastructure.
Layer 1 (Small Deployments (OS)) FREE:
- The ADK
- WDS – Enable in Windows Server Features
- High Time Cost
Layer 2 (Medium Deployments (OS + APPS + UPDATES) PAID $$:
- SCCM $$
- WSUS – up to you
- Lower time cost
- Higher cash cost
Layer 3 (Cloud Based Management (OS + APPS + UPDATES + SETUP DIRECT FROM MANUFACTURER) PAID $$$:
- Azure AD – Free
- If you have on-premise Active Directory then you need the Azure Active Directory sync tool on your Primary Domain Controller. -Free
- AutoPilot – Free
- Intune – PAID $$$
- Lowest time cost
- Highest cash cost
You will notice that it goes in order from FREE as in BEER, to you buy it you own it, and then a subscription service based model. It is important to perform a cost analysis because if you’re scale is large enough the PAID options can have a lower total overall cost.
After sifting through the internet I finally found something that resolved our performance issues with Sage 300. It seems that the issue in my case had to do with Windows AutoTune. The resolution was to disable it. I used a registry edit via GPO to apply to all Sage 300 ERP clients.
Here are the commands to
netsh interface tcp show global
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global autotuninglevel=normal
This way you can at least check if this resolves your issue or not before deploying a GPO.
Set to “0” for off and “1” for on. In my case the entry wasn’t there so it needed to be created.
For more info check the sources: