dennisgorelik: (Default)
New version of Skype deleted option to record custom voice mail greeting and deleted my custom voice recording message.

There is no way to record custom greeting now:

Why would Skype/Microsoft team delete that feature? Was it hard to manage?

My guess is that the reason for that feature deletion - is that Microsoft is pushing for new version of Skype: "Skype App".
"Skype App" seems to be designed for mobile phones and does not even have support for hotkeys.
dennisgorelik: (Default)
As long as Skype sucks, it’s pretty clear to everyone that Microsoft is in no danger of pioneering any revolutionary new UI paradigms when you have yet to master getting any of the old ones right yet.
Basic video conferencing with a little audio and a dumb camera are barely functional in the year 2017 and the clowns responsible for it are getting wall-to-wall press coverage about the fairy-tale technology they are contriving to solve tiny irrelevant problems, INSTEAD of making their own multi-billion dollar telecommunications platform work reliably so that I can ACTUALLY stay in my own home instead of having to constantly spend thousands of dollars traveling on businesses.
What if - you just made video conferencing so reliable that you put hotels, rental cars and the airlines completely out of business?

To be fair, telecommuting is getting better over time. Mostly because internet channels are getting faster and more reliable.
I do not need video, but I need a screen sharing.
Unfortunately Skype misbehaves when there are multiple people joining conference: screensharing may unexpectedly stop, participants may drop or simply do not hear each other...
dennisgorelik: (Default)
I bought NUC7i3BNH.
Then I tried to install Windows Server 2016 Standard on that NUC.
Windows Server installation itself was successful, but several drivers, including Network Adapters(!) and "Multimedia Audio Controller" - did not install.

Search for drivers brought me to:
where to my amazement I discovered that most of NUCs do NOT support Windows Server OS.

Further research pointed me to a hack that allows to manually use Windows 10 drivers on Windows Server 2016.
It goes like this:
1) Open C:\install\LAN_Server2016_64_22\PRO1000\Winx64\NDIS65\e1d65x64.inf
2) From this section:

copy these 3 lines:
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8&SUBSYS_00008086
%E15D8NC.DeviceDesc% = E15D8.10.0.1, PCI\VEN_8086&DEV_15D8&SUBSYS_00011179

into this section:

3) Then turn off drivers checks:
bcdedit /set TESTSIGNING OFF

4) And finally install the driver:
pnputil.exe -i -a C:\install\LAN_Server2016_64_22\PRO1000\Winx64\NDIS65\e1d65x64.inf

After that Network (and Internet) started working on my new NUC.

But I do not understand - why Intel does not allow these drivers under Windows Server 2016 by default?

Update: Windows Server 2016 on NUC7i3BNH struggles - part 2.
dennisgorelik: (Default)
Normally, in case of invalid input Uri() code throws UriFormatException. But with really weird input Uri(baseUri, Url) overload can produce NullReferenceException:
public void UriFailureTest()
    new Uri(
        new Uri(""),
dennisgorelik: (2009)
We tried to run PowerShell remotely (in order to automate build deployment).
We managed to make it work on developers' machines, but on production server it just refuses to work:
Windows PowerShell

PS C:\Windows\system32> Enable-PSRemoting -SkipNetworkProfileCheck -Force
WinRM is already set up to receive requests on this computer.
Set-WSManQuickConfig : <f:WSManFault
xmlns:f="" Code="2"
Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"
xmlns:f="" Code="2"
Machine="sv7731"><f:Message>Unable to check the status of the firewall.
At line:65 char:17
+                 Set-WSManQuickConfig -force -SkipNetworkProfileCheck
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
   + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand

PS C:\Windows\system32> Enter-PSSession -ComputerName localhost
Enter-PSSession : Connecting to remote server localhost failed with the
following error message : Access is denied. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ Enter-PSSession -ComputerName localhost
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : InvalidArgument: (localhost:String) [Enter-PSSes
  sion], PSRemotingTransportException
   + FullyQualifiedErrorId : CreateRemoteRunspaceFailed


Note "Unable to check the status of the firewall." part of the message.
Why would Enable-PSRemoting command try to check the status of the firewall?

Another Windows WTF reported by yatur

Finally we were able to fix this remote powershell issue.
The problem was in Group Policy for IpV4Filter on our production machine.
IpV4Filter was limited to a single IP address (main address of that production machine).
I have no idea why it was setup that way.

This is how I fixed WinRM localhost access problem:
Run gpedit.msc
Local Computer Policy
Computer Configuration
Administrative Templates
Windows Components
Windows Remote Management (WinRM)
WinRM Service
Allow remote server management through WinRM

In "IPv4 filter:" change "" to "*":
IPv4 filter: *


In the end, PowerShell and Microsoft server tools leave a negative impression due to bugs and pathetic diagnostic.

Consider another PowerShell surprise:
"ls" and "dir" commands produce empty output in case when folder is empty. No headers, no message that says there are no files. Just nothing. WTF?
dennisgorelik: (2009)
That was unexpected and I even thought it is a joke. But it is not a joke.

Why would Microsoft buy the largest job board?
Microsoft is in a different business.

1) What a terrible time to be burning that much cash, just before the next recession, and on a resume site. I was starting to see some good things coming from Microsoft but this makes me shake my head and question leadership big time.

2) I suspect major LinkedIn investors shopped around the company and financial-engineered a sophisticated kickback
dennisgorelik: (2009)
From: Bing Ads Support
Date: Wednesday, October 21, 2015, 12:53:47 PM EDT
Subject: SRX1309484828ID - Bing Ads Support Follow Up

Dear Sir/Madam,

I am writing you today regarding your concern on Universal Event Tracking. UET is one features in Bing Ads that helps you track the behavior of the customer once they visit your website. Pleased be inform that our campaign analytics tool is no longer working. I have prepared a resources for your reference to learn more information about our Universal Event Tracking.

Universal Event Tracking

I will now be closing you service request number 1309484828. You may reply to this email within 7 days if you do not feel that your concern has been resolved or call us at 800-518-5689 and we will immediately re-open your service request.

It looks like Microsoft is clueless in running advertising platform on pretty much all levels: product design, engineering, support.


dennisgorelik: (Default)
Dennis Gorelik

September 2017

34567 8 9
1011 12131415 16


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 23rd, 2017 05:48 am
Powered by Dreamwidth Studios