We just upgraded our VmWare environment to vSphere 6 with the vCenter installed on Windows 2012r2 using SQL server. The only problem we faced when we migrated the Windows scheduled task that run powercli command from the old 5.5 vCenter to the new one. Keep in mind that my powershell knowledge is very limited...
The task run weekly to return all the running VMs and also VMs with snapshot that are older than 7 days. After hours of investigation I finally found out that the script were running fine when ran directly from whitin powercli so the problem had to come from task scheduler. I found some blog page that suggested to test the scheduled task command with the parameter from the command prompt to see where things goes wrong. That proved to be the best troubleshooting option as I quickly realised that the script was running fine but all the vmware command were returning "invalid command name". This lead me to diagnose further and understand that the vim.psc1file is just a simple text file (powershell console file) instructing powershell to load specific module and/or snapin. I also discovered that you can create new powershell console file by using the export-console command, so I exported the console loaded from the powercli shortcut on the desktop and oh surprise the console file is different than the vim.psc1 created automatically from Vmware. I tested running my script with this powershell console file and tadam! The scripts all works again. The problem is that the default vim.psc1 file miss this line:
<PSSnapIn Name="VMware.VimAutomation.Core" />
This SnapIn is the one used for the get-vm command and was the one causing the problem.
jeudi 17 mars 2016
Citrix Netscaler - HTTP to HTTPs sharepoint page rewrite
The contex: sharepoint is accessed directly on http internally.
We came across a problem that some of our Sharepoint page have hardcoded link instead of dynamic link so when we expose the page externally the link are static to HTTP and since the page are accessed on a secure connection the browser complain that there is unsecure data accessed in clear text instead of SSL. The work around is to rewrite the page body when they are returned to the end user so that the link contained in the page are httpS instead of http. I tried doing rewrite response body without succes and then Citrix consultant suggested to use URL Transformation feature under AppExpert -> Rewrite -> URL Transformation instead that provided a working solution for us.
First we create the profile and enter a descriptive name: TrProfile_http-httpS
Now edit this profile to add an action by clicking on insert:
Name: http2https-action
Priority: 20
Enable = Check
Response URL From: http://(.*)
Response URL Into: https://$1
Click OK.
After that we create the Policies
Name: TrPol-http-https
Profile: TrProfile_http-httpS
Expression: HTTP.REQ.IS_VALID
Click OK.
Finally bind this transform Policy to a CS or LB Vserver:
Edit your Vserver, click the "PLUS" sign under policies, choose: transform -> Request and then bind your newly created transform policy: TrPol-http-https
Click OK, Click Done.
Now when the end users access the page, the Netscaler transform all http link in the page to https and we didn't need the developper to build a new page for external users.
We came across a problem that some of our Sharepoint page have hardcoded link instead of dynamic link so when we expose the page externally the link are static to HTTP and since the page are accessed on a secure connection the browser complain that there is unsecure data accessed in clear text instead of SSL. The work around is to rewrite the page body when they are returned to the end user so that the link contained in the page are httpS instead of http. I tried doing rewrite response body without succes and then Citrix consultant suggested to use URL Transformation feature under AppExpert -> Rewrite -> URL Transformation instead that provided a working solution for us.
First we create the profile and enter a descriptive name: TrProfile_http-httpS
Now edit this profile to add an action by clicking on insert:
Name: http2https-action
Priority: 20
Enable = Check
Response URL From: http://(.*)
Response URL Into: https://$1
Click OK.
After that we create the Policies
Name: TrPol-http-https
Profile: TrProfile_http-httpS
Expression: HTTP.REQ.IS_VALID
Click OK.
Finally bind this transform Policy to a CS or LB Vserver:
Edit your Vserver, click the "PLUS" sign under policies, choose: transform -> Request and then bind your newly created transform policy: TrPol-http-https
Click OK, Click Done.
Now when the end users access the page, the Netscaler transform all http link in the page to https and we didn't need the developper to build a new page for external users.
S'abonner à :
Messages (Atom)