Search This Blog

Wednesday, August 14, 2019

Add or remote server from the Lync pool

https://tomtalks.blog/2013/04/lync-2013-gotcha-when-addingremoving-fes-in-topology-publishing-topology-will-reset-the-relevant-pool/

https://docs.microsoft.com/en-us/skypeforbusiness/manage/topology/manage-front-end-servers


When you add or remove a server to the pool in your topology and then publish the updated topology, it will cause all of the servers in the pool to restart at the same time. While the servers are restarting the pool is offline, which will interrupt service for your users connected to that pool. To prevent any interruption of service to users, plan to publish the topology with the new server in the pool during non-business hours.

Windows 2019 server activation error

With a correct key, we can not activate Windows 2019 server:

"We can’t activate Windows on this device as we can’t connect to your organization’s activation server. Make sure that you’re connected to your organization’s network and try again."

The workaround is to do with command line - run as administrator:

slmgr.vbs /ipk   key-key-..



Wednesday, July 3, 2019

SharePoint 2013 install error 1603

if you get an error such as


Problem Event Name:                        OfficeClassicSetup
  SETUP EXE VERSION:                        15.0.4454.1000
  SETUP DLL NAME:                            SVRSETUP.DLL
  SETUP DLL VERSION:                        15.0.4709.1000
  ERROR CODE:                                   1603
  MSI HRESULT:                                   Unspecified
  ERROR DETAILS:                               FC73469E
  FIRST ERROR CODE:                         1603
  OS Version:                                       6.3.9600.2.0.0.272.7
  Locale ID:                                          1033



it may mean that you need to ad resources: check if you have 4vCPU, disk space 80GB+

Re.run setup


Wednesday, June 19, 2019

Offline IM for Skype and Lync

Offline IM -  a feature that allows you to get missed IM while you are offline is not avaiable for Lync 2013 server, but is for Skype for Business server: https://docs.microsoft.com/en-us/skypeforbusiness/deploy/im-and-presence/enable-or-disable-offline-im

Wednesday, May 29, 2019

CentOS 7 on Hyper-V 2016

CentOS 7 minimal installs happily on Windows Server Hyper-V 2016. Do not forget to run
nmcli
nmtui

to active network connection, as by default it is not active.


Thursday, May 16, 2019

SharePoint 2010 workflows - create a hyperlink

https://wonderlaura.com/2013/05/30/workflow-create-a-hyperlink/

Office 365 Exchange Online Protection and DMARC

If you want to protect your domain with DMARC or use DMARC to filter spam and you use Office 365, note that Microsoft decided to alter normal DMARC policy. Imagine the domain protects itself and a message was identified as DMARC=fail and policy is set to reject with 100%. DMARC policy example: v=DMARC1;p=reject;pct=100
Office 365 will ignore reject and will deliver email marked as spam. A header will contain

"dmarc=fail action=oreject" (oreject being overwritten reject.)

Here is how Microsoft justifies this design decision:

"If the DMARC policy of the sending server is p=reject, EOP marks the message as spam instead of rejecting it. In other words, for inbound email, Office 365 treats p=reject and p=quarantine the same way.
Office 365 is configured like this because some legitimate email may fail DMARC. For example, a message might fail DMARC if it is sent to a mailing list that then relays the message to all list participants. If Office 365 rejected these messages, people could lose legitimate email and have no way to retrieve it. Instead, these messages will still fail DMARC but they will be marked as spam and not rejected. If desired, users can still get these messages in their inbox through these methods:
  • Users add safe senders individually by using their email client
  • Administrators create an Exchange mail flow rule (also known as a transport rule) for all users that allows messages for those particular senders."


https://docs.microsoft.com/en-us/office365/securitycompliance/use-dmarc-to-validate-email#inbounddmarcfail

Monday, May 6, 2019

ICMP redirect

In the middle of migration from one firewall to another you may discover that you need to point a specific migrated IP to new firewall, while default gateway remains as old firewall.


Then in the old firewall you will specify a route to forward to new firewall.

When a user will ping that IP, the old firewall as default route will respond with ICMP redirect message.  This message will most problably be ingored by your user PC.

Check if the registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableICMPRedirect   is 1

and that Firewall allows ICMP Redirect messages (the best is to enable a custom Windows firewall rules to let this to be accepted in trusted networks, but not in public as example.


Then when you ping you will see ICMP redirect message in Wireshark, then after a while that your PC starts sending it to new Firewall.


Note that "route print" will not show this new route.





Wednesday, April 24, 2019

Tuesday, January 22, 2019

NetApps file share does not work via alias for Skype for Business


Log Name:      Lync Server
Source:        LS Storage Service
Date:          21.01.2019 13:55:45
Event ID:      32008
Task Category: (4006)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Unexpected exception.

Message=Error: Path \\fs_AppsData_.domain.com\Apps_Data$\SFBshare\1-WebServices-11\StorageService failed to be read for flushed data. Error details: System.IO.IOException: The account used is a computer account. Use your global user account or local user account to access this server.


The problem is that we use alias, if we change alias to server name, it works. This share is actually NetApp vfiler.

Here is a reference on how to add SPN for the alias. The alias is CNAME or A record.



Wednesday, January 9, 2019

Skype for Business Address Book normalisation rules

In the past Lync used txt files Company_Phone_Number_Normalization_Rules.txt to manage normalisation rules, with SFBit is now powershell Get-CsAddressBookNormalizationRule, etc.

By default it contains already some rules, but if you need to modify you can.

Here is a test tool that will show existing rules and will allow to test with a specific test number:
https://gallery.technet.microsoft.com/Skype-for-Business-Address-2ab65ca7


One thing remains unclear - the tool and all articles that I could find says that SFB will automatically strip spaces and other symboles like dashes from the phones number. However, I have an example where it does not work - when number is typed in contact lookup in SFB client the string must match exactly the string in AD phone field, otherwise the contact is not proposed. For the moment I do not know why. In another installation it work ok. It looks like something related to either client version  or method (web search only) or client  or GPO policy - had no time to analyse further.