How to remove custom template information from word document (doc/docx) before sending.

Sometime you may use a custom template to build the document and then later you may want to  remove such information from the documents properties before distribution.

doc_docx_template_properties_screenshot

The steps are as below:
Removing the template information without removing all other “personal” data:

Open Word. Click “File” and then “Options” on the bottom of the left sidebar.

The Word Options dialog provides you with a variety of settings to help you manage Word.

Click “Add-Ins” on the left sidebar. A list of Microsoft Office Add-ins appears under Add-Ins. Select “Templates” in the box next to Manage at the bottom and then click the “Go%u2026” button.

The Templates and Add-Ins dialog opens with your current template listed in the field under Document Template.

Open Word. Click “File” and then “Options” on the bottom of the left sidebar. The Word Options dialog provides you with a variety of settings to help you manage Word.

Click “Add-Ins” on the left sidebar. A list of Microsoft Office Add-ins appears under Add-Ins.

Select “Templates” in the box next to Manage at the bottom and then click the “Go%u2026” button. The Templates and Add-Ins dialog opens with your current template listed in the field under Document Template.

Delete the current template name and select OK. (alternatively select “Attach” and choose Normal.dotm).

In the properties summary the template should now show as: normal.dotm

Advertisements
Categories: Microsoft, Tools

Which IBM hardware can run which OS ?

pSeries (POWER-based Platform, currently P8): AIX (=IBMs UNIX), Linux (SuSe, Ubuntu), iOS (formerly known as AS/400)
zSeries (mainframes): z/OS (replaced MVS, OS/390 and VM), z/Linux
xSeries (=Intel-compatible): Linux and everything else running on Intel-systems.
pSeries systems can use either the IBM hypervisor which runs iOS-, AIX- and Linux-LPARs or (only Power8) the Power-KVM (=Linux’ KVM adapted for pSeries) with Linux-Systems as LPARs. Notice, however, that Power-KVM has a slightly smaller throughput than IBMs hypervisor.
zSeries can run z/OS and z/Linux
For xSeries the same as for any Intel-compatible PC applies.

Categories: IBM, Linux, Tools

Skype 2016 + Sharepoint 2013 + Skill Search Not Working

If your sharepoint certificate has expired you need to renew it

Then install it via IIS or Install in on the sharepoint server 2013 Key Store and bind the new certificate to the IIS https settings

Do a restart of IIS

Test people search  in sharepoint with a keyword.

Test skill search with keyword in Lync 2013 or Skype for Business

REF: https://techontip.wordpress.com/2011/06/06/how-to-create-a-san-certificate-signing-request-for-iis-web-server/

Categories: Programming

Sending Email Alert BAT File with PowerShell

Include below line in the bat file (Assuming you have powershell installed and enabled for running in this way)

powershell -ExecutionPolicy ByPass -Command Send-MailMessage -SmtpServer “xxx.xxx.xxx” -To “user@domain.com” -From “sender@domain.com” -Subject “Testing” -Body “123”

Microsoft VMM Build Version Numbers

Microsoft Exchange : The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota

—————————
Microsoft Exchange
—————————
Starting a command on remote server failed with the following error message : The WinRM client sent a request to the remote WS-Management service and was notified that the request size exceeded the configured MaxEnvelopeSize quota. For more information, see the about_Remote_Troubleshooting Help topic.
—————————
OK
—————————

FIX: http://wgsnetman.blogspot.com/2012/12/exchange-2010-um-and-wmf-30.html

C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\PowerShell

<OperationsConfiguration MaxOperationTimeoutSeconds=”900″ MaxShellIdleTimeoutMinutes=”15″ MaxEnvelopeSizeKB=”8192″/>

 

 

Categories: Exchange 2010, Microsoft

Setup has detected that Visual Studio 2015 Update 3 may not be completely installed. Please repair Visual Studio 2015 Update 3, then install this product again.

Open a elevated comand prompt and run

“DotNetCore.1.0.0-VS2015Tools.Preview2 (1).exe” SKIP_VSU_CHECK=1

If you get

Setup has detected that Visual Studio 2015 Update 3 may not be completely installed. Please repair Visual Studio 2015 Update 3, then install this product again.

Categories: Programming, Visual Studio