Harold Bato, vTSP

VMware 6.5 vCenter High Availability (VCHA) Limitations

noreply@blogger.com (Harold Bato) — Tue, 15 May 2018 21:43:00 +0000

As per VMware vSphere 6.5 testing (currently on 6.5 U1), there are currently 2 known limitations on automatic failover on vCenter High Availability (VCHA)

Loss of Management or Public Network

If your VC Nodes can still communicate within heartbeat network, automatic failover will not occur.

vSphere Web Client Service Failure.

Service failure of web client does not trigger automatic failover due to several factors that could cause service failure. And even though web client service is not running, key APIs could still be functional.

SCCM MSI: Could not access network location %APPDATA%\

noreply@blogger.com (Harold Bato) — Fri, 28 Mar 2014 03:20:00 +0000

A very frustrating error when installing the agent. All when you thought that the setup was running fine and easy (for~4000+ clients) some of them just don't get installed!

So looking at the ccmsetup log, I found out this:

MSI: Could not access network location %APPDATA%\

Resolution, check the registry of each *sob* clients that we're left out. Here's the registry:

HKEY_USERS\S-1-5-18\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

Look for "AppData" and change the value to " %USERPROFILE%\AppData\Roaming"

That's it! Wait for the setup to reinitialize which is about 2 hours.

Add Multiple Discovered/Managed Computer to a Collection - SCCM 2007/2012/2012 R2

noreply@blogger.com (Harold Bato) — Fri, 21 Mar 2014 02:29:00 +0000

After doing some research, here's the script I've used to add a list of computers to a certain collection using a batch file. Basically there are three parts of the script:

1. comp.txt - contains the list of computers to be added

2. addcompresid.vbs - contains the script that adds computers to the collection.

3. batch.bat - contains the script to add computers from comp.txt using addcompresid.vbs script.

Instructions:

1. Copy and create (probably from notepad) the batch.bat and addcompresid.vbs

2. Edit Set objSWbemServices= objSWbemLocator.ConnectServer on addcompressid.vbs to specify which MP you are going to connect.

3. Edit Set _COLID on Batch.bat to specify the collection ID. This can be found on the properties of the collection.

4. On the same folder, create comp.txt and paste all the computers to be added.

So here's the script and enjoy!

_________________________________________________________________

Batch.bat

@echo off

Set _COLID=COLLECTION

Set _log=AddToCollection.log

echo Starting log file > %_log%

for /f %%a in (comp.txt) do call :AddComp %%a

goto :eof

:AddComp

cscript //nologo AddCompResID.vbs %1 %_COLID%

Echo. Adding Computer %1 to SCCM CollectionID %_COLID%

Echo. Adding Computer %1 to SCCM CollectionID %_COLID% >> %_log%

goto :eof

_________________________________________________________________

addcompresid.vbs

strCompName = Wscript.Arguments.Item(0)

strCollID = Wscript.Arguments.Item(1)

Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")

Set objSWbemServices= objSWbemLocator.ConnectServer("MPSERVER","root\sms")

Set ProviderLoc = objSWbemServices.InstancesOf("SMS_ProviderLocation")

For Each Location In ProviderLoc

If Location.ProviderForLocalSite = True Then

Set objSWbemServices = objSWbemLocator.ConnectServer _

(Location.Machine, "root\sms\site_" + Location.SiteCode)

End If

Set colCompResourceID = objSWbemServices.ExecQuery("SELECT ResourceID FROM SMS_R_System WHERE " & _

"NetbiosName='" & strCompName & "'")

For each insCompResource in colCompResourceID

strNewResourceID = insCompResource.ResourceID

Set instColl = objSWbemServices.Get("SMS_Collection.CollectionID=""" & strCollID & """")

Set instDirectRule = objSWbemServices.Get("SMS_CollectionRuleDirect").SpawnInstance_()

instDirectRule.ResourceClassName = "SMS_R_System"

instDirectRule.ResourceID = strNewResourceID

instDirectRule.RuleName = strComputerName

instColl.AddMembershipRule instDirectRule

_________________________________________________________________

Bypass HTTPS or SSL Requirement for Citrix Receiver

noreply@blogger.com (Harold Bato) — Thu, 29 Aug 2013 02:29:00 +0000

For those of you doing POCs or Testing Lab, here's how to disable SSL or HTTPS requirement for Citrix Receiver.

To bypass SSL, open regedit.exe on the client workstation and go to:

For 64-bit

HKLM\software\wow64\citrix\authmanager

For 32-bit

HKLM\software\citrix\authmanager

Create string with value:

ConnectionSecurtiyMode = Any

And also, go to:

For 64-bit

HKLM\software\wow64\citrix\dazzle\AllowAddStore

For 32-bit

HKLM\software\citrix\dazzle\AllowAddStore

And set the value to "A" and restart the receiver.

This is also useful for those troubleshooting connection between Citrix Receiver and Xenapp Server. But take note though that this is not recommended for production environment since you are exposing the user's credentials in the network.

Preview of Windows Server 2012 R2, System Center 2012 R2 and SQL 2012 R2 are now available for download

noreply@blogger.com (Harold Bato) — Tue, 25 Jun 2013 07:55:00 +0000

I've recently received the email from MSFT that these products are now available for download:

Windows Server Evaluations

System Center and Windows Intune Evaluations

SQL Server Evaluations

Can't wait to check them out especially on Hyper-V!

You may check the whole list here at http://technet.microsoft.com/en-US/evalcenter/dn205292

The installed version of SQL Server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information.

noreply@blogger.com (Harold Bato) — Fri, 14 Jun 2013 06:45:00 +0000

I got a very interesting error today while working with multiple SCOM 2012 Server across different data centers and here's what I got:

The installed version of SQL Server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information.

Here's the scenario when I encountered the error:

1. Installed the first SCOM 2012 Server located on Data Center 1.
2. Installed second SCOM 2012 Server also on Data Center 1.
3. Installed third SCOM 2012 Server on Data Center 2 and enocuntered the error.

Here's the solutions that resolved the issue:

1. Make sure that the credentials used in installing SCOM 2012 have rights on the remote SQL Server.
2. Verify connectivity between Server and Remote SQL Server.
3. Check firewall ports on Remote SQL Server.
4. *this resolved my issue* Do a WBemTest from the Server to the Remote SQL Server. If you get "RPC Server Unavailable", it means that RPC Ports are blocked, either at the Remote SQL Server or your network firewall. Make sure to open RPC ports 135, 137, 139 and 445 to resolve this issue.

This error may be due to SCOM Setup unable to determine the version of SQL on the Remote Server and thus displaying the error message.

Wireless on Windows Server 2012

noreply@blogger.com (Harold Bato) — Thu, 21 Mar 2013 01:35:00 +0000

I've recently installed Windows Server 2012 on my laptop for testing and lab purposes and what do I get, I cannot connect to the wireless router!

So here's how to enable wireless networking on Windows Server 2012 (not recommended for production servers)

1. Go the Server Manager
2. Click Add Roles and Features
3. Go to Features List
4. Enable Wireless LAN Service
5. Add the Feature and restart

Installing System Center Virtual Machine Manager (SCVMM) 2012 SP1

noreply@blogger.com (Harold Bato) — Sat, 02 Mar 2013 16:12:00 +0000

1. Logon to the server using SCVMM Service Account.

2. Download and install Windows Assessment and Deployment Toolkit (http://www.microsoft.com/en-us/download/details.aspx?id=30652)

3. Start the installation wizard for SCVMM 2012 SP1.

4. Under Select Features to install, select both Management Server and Console.

5. Enter your Username and Organization and input the Product ID(if no product key was typed, SCVMM will go into evaluation mode).

6. Accept the License Agreement.

7. Confirm to join or not the Customer Experience Improvement Program (CEIP)

8. Turn on/off the Microsoft Update

9. Select default installation location.

10. Verify Pre-Requisites.

11. Under Database Configuration, input your SQL Server on Server Name, Port 1433 under Port, your SQL Instance for Instance Name and select New Database – VirtualManagerDB.

12. Under Configure service account and distributed key management, select Domain Account and input your SCVMM Service Account and its password.

13. Select default Port Configuration.

14. Select default Library Configuration.

15. Verify the Installation Summary and start the installation.

Permissions for System Center Orchestrator runbooks

noreply@blogger.com (Harold Bato) — Sat, 16 Feb 2013 17:23:00 +0000

Okay, here's a good scenario on System Center Orchestrator. You create a runbook that connects to a remote server. You tried to start/stop a service but it failed or gives you a warning or error. So how do you resolve this issue?

I've tried so many other ways as being told in other sites but the simplest thing worked out for me.

Add the Orchestrator run as account as local administrator on remote server that the runbook is working with. And whoala, the runbook can now start/stop a service!

If you want to check other permissions required, check it out here.

Free Microsoft Jacket! Join the MCSA Challenge!

noreply@blogger.com (Harold Bato) — Tue, 12 Feb 2013 16:00:00 +0000

Limited edition jacket for those who are taking the MCSA Certfications. See image below for more details. (Upgrade certifications are not accepted; you must take the entire set of exams to qualify)

Visit Microsoft Partners Philippines for more details.

Officially A Microsoft V-TSP

noreply@blogger.com (Harold Bato) — Tue, 12 Feb 2013 15:40:00 +0000

This is a great day! I'm now officially selected a Microsoft vTSP! I'll be working closely with MSFT with regards to Pre-Sales and Implementation of Hyper-V 2012, WS 2012 and System Center 2012.

So what's a vTSP? I've googled down and found this this phrase from Ryan:

The Microsoft Virtual Technology Specialist Program (VTSP) is a select group chosen from the elite in Microsoft’s partner community, whose focus is to augment Microsoft’s internal Technology Specialist team. Their primary role is to communicate the value of Microsoft Solutions to customers and to provide architectural guidance for Enterprise Integration solutions. The Microsoft VTSP program was designed to create a deeper relationship with Microsoft Partners, the Product Teams at Microsoft Corporate, and Regional Microsoft Offices, in order to provide highly skilled solution specialists to Microsoft customers. It is designed to enable a high performance team of partner-based resources to deliver pre-sale activities and resources to empower customers and help them meet their solution and integration needs.

I'm hoping to learn more from this program and hope to level up more in this industry of Cloud Computing!

SCOM Management Servers Greyed out

noreply@blogger.com (Harold Bato) — Tue, 12 Feb 2013 15:38:00 +0000

I recently found out this morning that my SCOM Server was down and after logging in to my SCOM I see that my management server is greyed out.

Partial fix that worked for me was to fix the error first that says " partitioning and grooming processes for the operational database (OperationsManager) on the server scom, 1433 have either not been run recently or have been failing. At the time this alert was raised, the partitioning and grooming process had not completed for 1 days." Verify the SQL server if there are any errors and the SCOM events. After that let the error resolve on its own. If the management server wont go green, restart the affected SCOM server.

SCSM 2012 Self-Service Portal Access Denied

noreply@blogger.com (Harold Bato) — Sun, 10 Feb 2013 12:40:00 +0000

If you're getting an error from Service Manager 2012 Self Service Portal which looks something like this:

Error: Access Denied

Here's how to resolve the issue:

Logout and Sign in as a Sharepoint Administrator.
From SCSM 2012 Portal, select Site Permissions (located on Sharepoint Tab).
You'll see a warning "This Web site inherits permissions from its parent (Team Site)". Select Manage Parent.
Select Grant Permissions.
Add the group/users of choice, to give general permissions, add the group Domain Users and make sure to tick/give Read Permissions.

Basically, after installing Service Manager 2012 Web Parts, the only user that can access the Self-Service Portal is the Sharepoint Administrator. So make sure to add the required users to the list after installing the Web Parts.

SCSM 2012 Web Part on Windows Server 2012

noreply@blogger.com (Harold Bato) — Sun, 10 Feb 2013 12:15:00 +0000

I've recently encountered one of the strangest flaw on SCSM 2012, and it's installing all of Service Manger 2012 Web Part on Windows Server 2012.

So let's review the requirements:

Windows Server 2008 R2 RTM or with SP1
IIS 7.5 with IIS 6 metabase compatibility installed
Self-signed SSL certificate
ASP.NET 2.0
Microsoft .NET Framework 4.0
Microsoft Analysis Management Objects
Microsoft SharePoint Foundation 2010
Or Microsoft SharePoint Server 2010
Or Microsoft SharePoint 2010 for Internet Sites Enterprise
Excel Services in SharePoint 2010 is required for hosting dashboards for advanced analytical reports

So to install Service Manger 2012, you're going to need Sharepoint 2010, may it be Foundation or Server. But note that Sharepoint 2010 only supports up to Windows Server 2008 R2. Even if you have SP1, still it's a no go. And Sharepoint 2013 is not supported by Service Manager 2012.

So the answer to the question on can we install all of Service Manager 2012 Web Parts on Windows 2012? NO, you cannot install ALL Service Manager Web Parts until an SP2 for Sharepoint 2010 or Service Manager 2012 receives an SP2(that provides support for Sharepoint 2013). What you can do (if you still want to use Windows Server 2012) is to have a separate Sharepoint Server on Windows 2008 R2 and let it host the Sharepoint Web Part.

Free Upgrade for Microsoft Certified IT Professionals

noreply@blogger.com (Harold Bato) — Fri, 08 Feb 2013 13:48:00 +0000

For those who with the following certifications:

MCSA: Windows Server 2008

MCITP: Virtualization Administrator

MCITP: Enterprise Messaging Administrator

MCITP: Lync Server Administrator

MCITP: SharePoint Administrator

MCITP: Enterprise Desktop Administrator

You can get free vouchers to upgrade to:

MCSE: Desktop Infrastructure
MCSE: Server Infrastructure
MCSE: Private Cloud

So what are you waiting for? Grab the link here and start preping for the exams! By the way, these exams comes with Second Shots!

*These vouchers expire on Dec 31st, 2013. All exams and retake exams in the pack must be taken by December 31st, 2013.*

Windows Server 2012 Upgrade Jump Start

noreply@blogger.com (Harold Bato) — Fri, 08 Feb 2013 13:41:00 +0000

For those who are looking for training videos on Windows Server 2012, you might be interested in these videos for jump start training here.

These videos are intended for those who would want to upgrade their MCITP certifications to MCSE: Desktop Infrastructure, or MCSE: Server Infrastructure, or MCSE: Private Cloud.

The partner transaction manager has disabled its support for remote/network transactions

noreply@blogger.com (Harold Bato) — Thu, 07 Feb 2013 16:17:00 +0000

As a lesson learned, when doing two way replication on SQL Servers, make sure to enable Network Access to MS DTC. To enable it do the following steps:

1. Go to Run > dcomcnfg.exe
2. Expand Console tree and find DTC
3. Click on local dtc > properties
4. Go to Security Tab
5. Enable Network DTC Access
6. Check inbound & outbound (whichever is required)
7. Check Client Administration
8. Use compatible authentication, mutual has the highest security.

Reference:
http://technet.microsoft.com/en-us/library/cc753620(v=ws.10).aspx

Invoke or BeginInvoke cannot be called on a control until the window handle has been created

noreply@blogger.com (Harold Bato) — Thu, 07 Feb 2013 16:16:00 +0000

What a pain! This error has been bugging me since morning and thankfully I have found a way of resolving this.

*Note: This has been tested on Windows 2008 R2 while installing SQL 2008.

The problem seems to be on the .NET 3.5 installation that you did as a prerequisite for SQL 2008. To resolve this we need to add another feature.

1. Go to Server Manager
2. Add a new feature
3. Select Windows Process Activation Services
4. Check .NET Environment
5. Install SQL 2008 again

Some users find that closing all running applications except the SQL Installation works.

Transferred from Weebly!

noreply@blogger.com (Harold Bato) — Thu, 07 Feb 2013 16:02:00 +0000

I'm transferring my blog to Blogger.com because buying a domain with weebly is too much of a pain. So hold on while I transfer all the contents of my blog to this new one.