which country user step here?

Tag Cloud

MOSS (47) SharePoint 2007 (37) SharePoint 2013 (30) SharePoint 2010 (23) MOSS admin (17) PowerShell (17) admin (17) developer (16) List (15) WSS (14) sql query (14) MOSS SP2 (13) end user (11) scripting (11) wss V3 (11) permission (9) sql (9) Moss issue (8) search (8) database (7) RBS (6) Service Pack (6) reportadmin (6) workflow (6) Excel (5) client object model (5) CU (4) Client Code (4) Command (4) Cumulative Updates (4) IIS (4) Patch (4) SharePoint designer (4) office 365 (4) stsadm (4) ASP.NET (3) Content Database (3) Groove (3) Host Named Site Collections (HNSC) (3) Tutorial (3) alert (3) batch file (3) codeplex (3) error (3) incomming email (3) restore (3) upload (3) user porfile (3) Caching (2) Folder (2) Index (2) Internet (2) My Site Cleanup Job (2) My Sites (2) News (2) People Picker (2) Share Document (2) SharePoint 2016 (2) SharePoint 2019 (2) View (2) Web Development with ASP.NET (2) add user (2) audit (2) authentication (2) coding (2) column (2) deploy solution (2) domain (2) download (2) enumsites (2) exam (2) export (2) issue (2) june CU (2) load balance (2) mySites (2) network (2) orphan site (2) performance (2) profile (2) project server (2) query (2) security (2) server admin (2) theme (2) timer job (2) training (2) web master (2) web.config (2) wsp (2) 70-346 (1) 70-630 (1) AAM (1) Anonymous (1) Approval (1) AvePoint (1) Cerificate (1) Consultants (1) Content Deployment (1) Content Type (1) DOS (1) DocAve 6 (1) Document Library (1) Drive Sapce (1) Excel Services (1) Export to Excel (1) Feature (1) GAC (1) Get-SPContentDatabase (1) Get-WmiObject (1) HTML calculated column (1) ISA2006 (1) IT Knowledge (1) ITIL (1) Install (1) Link (1) MCTS (1) Macro (1) Migration (1) NLBS (1) Nintex (1) Office (1) Open with Explorer (1) ROIScan.vbs (1) Reporting Services (1) SPDisposeCheck.exe (1) SQL Instance name (1) SSRS (1) Sandbox (1) SharePoint Online (1) SharePoint admin (1) SharePoint farm (1) Shared Services Administration (1) Site Collection Owner (1) Site template (1) Skype for business (1) Steelhead (1) Teams (1) URLSCAN (1) VLOOKUP (1) WSS SP2 (1) XCOPY (1) abnormal incident (1) admi (1) app (1) application pool (1) aspx (1) availabilty (1) backup (1) binding (1) blob (1) branding sharepoint (1) cache (1) calendar (1) change password (1) connection (1) copy file (1) counter (1) crawl (1) custom list (1) domain security group (1) event (1) excel 2013 (1) facebook (1) filter (1) fun (1) group (1) iis log (1) import (1) import list (1) improment (1) interview (1) keberos (1) licensing (1) log in (1) metada (1) migrate (1) mossrap (1) onedrive for business (1) operation (1) owa (1) process (1) publishing feature (1) resource (1) send email (1) size (1) sps2003 (1) sql201 (1) sql2012 (1) sub sites (1) system (1) table (1) task list (1) today date (1) trial (1) vbs (1) video (1) web part (1) web server (1) widget (1) windows 2008 (1) windows 2012 R2 (1) windows Azura (1) windows account (1) windows2012 (1) wmi (1)

Thursday, May 14, 2020

Change DocAve Agent service Account Password

After change the service account at AD , we need to change on DocAve manger platform only can continue to use it.

Change at DocAve Manager Server

1. Log in to the server hosting DocAve Manager

2. Open the Manager Configuration Tool

3. Key in the new password at section:

  • Control Service Configuration
  • Control Database Settings
  • Report Database Settings
  • Auditor Database Settings

4. Click Apply to save the settings

if the DocAve windows services is running on the Service account , we also need to reenter the password and restart the service for docave 6 Media service , Report Service , Timer Service.

Re-type the new password at DocAve Manager Manage Account Profile
1.      Login to the DocAve Manger, control panel > Managed Account Profile and check on the service account
2.      After selected the account click on Edit and retype the new password and click Save
3.      Password change is complete and just close the control panel.

Tuesday, October 8, 2019

How to read the SharePoint Security Audit Report

User request to check who's remove the permission !!!   As a SharePoint Admin we can get the information from the audit report ( anyway need to enable it before else will not have data available)

Site Settings > Audit log Reports : Select the Security settings

Once you get the report , we can get the information from the report .

Information below from the column good enough to find out who change the permission

User ID : Person done the change

Event Data : what permission is change (but is in number , so the number is represent the role showed as following )

Full Control 1073741829
Contribute 1073741827
Read 1073741826

This id is given by SharePoint , you can get it by do some programming or script.

  1. Go to the sites with /_layouts/15/people.aspx?MembershipGroupId=0
  2. You will see all the user over here, mouse over the id then you can see the left hand side bottom have the full URL detail showed . you can see the id here.
This information is showed what change is going on

Tuesday, March 19, 2019

SharePoint Performance : After SQL upgrade

Issues : Performance problems

Root Cause :  SQL compatibility level  of 130 or 140 which caused decreased query performance and increased CPU usage on the database server.

Resolution : Changing the compatibility level to 110 resolved the performance problems

How to fix :

We strongly recommend that you set the database compatibility level to 110 for SharePoint Server 2016 content databases. To change the compatibility level, run the following TSQL command:


You can view the compatibility level of all the databases in an instance of SQL Server by using the following TSQL query:

SELECT name, compatibility_level FROM sys.databases

 Detail URL :

This also applied to SharePoint2013 ( when you upgrade to SQL server and new content database version will created under compatibility level 120 )

Wednesday, March 13, 2019

OWA License

Issues : User unable to edit the excel online (OWA - Office Web Apps ) 

root cause : User is not inside the license group

Step to verify your valid license is for which user  :

  • log in to sharepoint server run following command : Get-SPUserLicenseMapping
  • Result will show as following :

Identity       : 6a120a5b-a14c-4cb7-b37e-xxxxxxx
License        : OfficeWebAppsEdit
Name           : ABC\arepointOWALic  >> this is the domain group have license to use edit at OWA
ClaimValue     : S-1-5-21-1008349960-1601062091-620655208-60439
OriginalIssuer : Windows

Solution : add use to the group (make sure your business policy is allow) then solved.

for more information about the  map user license enforcement can get from here :

Managing licenses can already be a headache, but it can be even more painful when SharePoint is involved because it has so many features that are specific to a license type. User License Enforcement is a new SharePoint 2013 feature that allows administrators to assign specific license features by mapping those license features to users in specific Active Directory groups. This article will show you how to utilize SharePoint’s new licensing capabilities, which gives administrators better control of how licensed features are managed and assigned to users.

New SharePoint Licensing Features = New Admin Abilities

In previous versions of SharePoint, when a server was activated with the Enterprise feature, it was very difficult to determine which users actually used the Enterprise and Standard features. In most cases, administrators would deploy another server that only had Standard features activated, and they would try to restrict users to accessing only that server. Sometimes they would even resort to deploying separate SharePoint farms to ensure the correct licensing was used. These methods resulted in over-deploying servers, which increased deployment costs.
The new licensing features will give administrators the ability to deploy a server with all the features, both Enterprise and Standard, but they will restrict users to use only the licensed features to which they are assigned. This can be cost effective for many organizations, as it can reduce the amount of servers that need to be deployed. Smaller organizations can utilize a single farm for blended licenses, such as deploying Project Server for certain users while still providing Standard Cals for majority of their business users. Note: SharePoint web applications must use Claims-based authentication; however, since that is the default in SharePoint 2013, you either will need to be moving towards Claims-Based or already be using Claims-Based Authentication.
SharePoint 2013’s user license enforcement is disabled by default and must be enabled before enforcement can begin. User License Enforcement configurations can only be completed in PowerShell using the eight available cmdlets.
The license CAL assignments that can be mapped to users are divided into five categories:
  • Standard – Delivers the core capabilities of SharePoint, including basic Search functions and Communities platform
  • Enterprise – Provides all the Standard Cal features, including the following Enhanced Search, Business Solutions (Access Services, InfoPath Services), and Business Intelligence (Excel services, PerformancePoint Services, and Visio Services)
  • Project – Access to Project Server that is installed within the SharePoint farm
  • DUET – Allows interoperability with SAP applications
  • WAC – Access to Office Web Apps
Enforcement is completed by mapping a security group in Active Directory to one of the five license categories, then adding users to the security groups. When the user in the AD group logs into SharePoint, usage data gets logged onto the farm. When the user attempts to access an unlicensed feature, they are blocked. License enforcement can be applied at different levels, such as site pages, document libraries and lists, so proper license mapping planning should be done to ensure users are correctly mapped.

Enable and Map User License Enforcement

Enable user licensing:

  • Start the SharePoint Management Shell.
  • Type the following cmdlet to enable license enforcement on the farm: Enable-SPUserLicensing
enable user licensing_SharePoint 2013
  • To confirm that licensing enforcement has been abled, use the Get-SPUserLicensing cmdlet. You should see the “true” value.
enable user licensing_SharePoint 2013

Map licenses to AD group:

  • Start the SharePoint Management Shell.
  • Type the following cmdlet to map license categories to AD security groups (change “yoursecuritygroup” with the name of your AD group to which you want it to map): $a=New-SPUserLicenseMapping -SecurityGroup yoursecuritygroup -License Enterprise
Map licenses to AD group_SharePoint 2013

  • $a | Add-SPUserLicenseMapping
Map licenses to AD group_SharePoint 2013
The User License Enforcement in SharePoint 2013 adds more management capabilities for licensing than previous versions, but it is the not the complete solution for ensuring licensing compliance. You will still need to do your reporting and license reconciliation to ensure that you have purchased the appropriate amount of licenses used. If you’d like, check out this further reading on SharePoint 2013 licensing.

Wednesday, February 27, 2019

Office 365 "Play Ground"

As for see now a day SharePoint Online is getting hot and popular , to support the SharePoint online task some big organisation only grant the SharePoint Online admin role for SharePoint Admin to manage the SharePoint Online only.

without the O365 ( Office 365) Global admin right you are unable to explore more function at Microsoft 365 admin center

as i have notice microsoft have free trial offer 1 year for Office 365 developer program , you can register the program and get the free trial at office 365 as Global Admin ( you can try what ever you want at the O365 , off course not include those premium service)

This program have up to 25 Office 365 Enterprise E3 Developer License , which is allow you to play around the product :

  • Exchange Online
  • SharePoint Online
  • Teams Online ( take over Skype of business )
  • Azure Active Directory 
  • other ...

Here you go for the URL : https://developer.microsoft.com/en-us/office/dev-program

have fun about it to ready your self for Cloud SaaS generation !!