HPE Software Products: Data Center Automation
Share |

Best of Show on Tour 2017: April 5 in Zurich/SwitzerlandOpen in a New Window

Join us for the Best of Show on Tour stop on April 5 at the HPE Offices in Zurich/Duebendorf where we will present the highlights of Discover London. Explore the current trends and developments in IT Operations Management. Learn how to master the challenges of digitalization without endangering IT operations. Agenda topics include: IT Operations – enabler of the Digital Enterprise; innovations in HPE Operations Bridge; integration of cloud-based services into HPE Operations Bridge-based monitoring; case studies for transforming into service-oriented IT operations. Don’t miss this opportunity and register now! (The event will be conducted in German language.)

Agenda & registration

 

Introducing Data Center Automation 2017.01 – New Year, New SuiteOpen in a New Window

This year, we’re completely revolutionizing HPE’s Data Center Automation (DCA) suite!

DCA 2017.01 is part of a continuous evolution towards a suite solution that unifies infrastructure management across infrastructure tiers and simplifies the consumption experience. We’ve brought infrastructure management under a single entitlement framework. Customers now have the flexibility of consuming and scaling the suite solution across different infrastructure tiers, without the need to manage licensing for individual infrastructure ecosystems. We’ve also introduced stand-alone compliance. Customers can run compliance independently, without having to coordinate complex scheduling with resource-heavy data center tasks such as provisioning and patching. This is the advantage of modularization - capability consumed freely, by itself, and scaled on demand. Lastly, in the theme of efficient infrastructure management, we’ve added an analytics pillar, starting with analytics-driven capacity and performance optimization for virtualized environments. Based on near real-time data, customers can right-size their VM environment, forecast capacity needs and intuitively identify any bottlenecks. 

In short, the DCA suite is a unified infrastructure management solution to automate tasks, orchestrate IT processes, enforce compliance and optimize infrastructure.  

Register for our upcoming webinar – “Data Center Automation: A new year, a new suite” here and learn more about how this new offering will revolutionize infrastructure management.

 

 

DCA Premium : from 2016.01 to 2016.10 ?Open in a New Window

Hello,

Is there any documentation describing how to upgrade the 2016.01 version of DCA to the new 2016.10 ?

 

Thanks a lot,

 

admin password not asked for during installOpen in a New Window

Hello,

I have just installed DCA express edititon as a VMware image. When I installed it, I got the usuall questions (IP address, root password and such), but not for the admin password. I even deleted the install and ran it again, but the admin password question is still missing. And now I'm unable to log on.

Any ideas as to how to fix it?

Kind regards
Harald Bjørnstad

 

 

 

Next DCAA ReleaseOpen in a New Window

Hi Team

When the next DCAA version will be released ?

Thx

 

DCA cannot rollout ESXi 5.5 Hosts using the iLO of Gen 9 ServersOpen in a New Window

Hi all,

we are facing a serious issue in the DCA 2016.1 Premium solution.

The following environment:

1. We cannot use dhcp, since this is filtered on the customers network

2. We have to use the (in the DCA) build-in SA version 10.21 for the ESXi Installation

Due to the network restrictions we have to use the following parameter:

hpsa_config

with a content like this:

{
"hostname": "name.fqdn.com,
"interfaces": [{
"macAddress": "3c:a8:2a:0d:4d:e4",
"vlanid": 0,
"enabled": true,
"dhcpv4": false,
"ipv6Autoconfig": false,
"provisioning": true,
"dnsServers": [
"10.10.130.2"
],
"staticNetworks": [
"10.13.243.22/255.255.255.224"
],
"ipv4gateway": "10.13.243..1"
}]
}

This one is attached to the iLO Object we setup in the unprovisioned server section in the SA Client.

Now we are starting the deplyment process and the iLO restarts the Server (Step 3 in the ProLiant OS - ESXi 5.5 U2 Scripted Install Buildplan).

The Proliant starts into the Intelligent Provisioning and thent it times out after the 20 minutes preconfigured delay.

I assume that the Intelligent Provisioning 2.4 and 2.5 are not supported from SA 10.21

Here is the output of the error message in the Job Log:

RROR:
ID: HPSA-1155
Code: com.opsware.script.ScriptMessageSpec.NON_ZERO_EXIT_CODE
Details: The exit code from the script was 100.


STANDARD OUT (the last 10 KB):
Running OS Build Plan DTAG ProLiant OS_2 - ESXi 5.x U3 Scripted Install (OSBuildPlanRef:2090001) against server (ServerRef:7720001)

Step 1 of 20: Run OGFS Script 'Validate Gateway Setting for Static Network Configuration'
Skipping gateway validation
No static network configuration details has been specified


Step 2 of 20: Run OGFS Script 'Check iLO Service'
Service active, version ILO4.


Step 3 of 20: Run OGFS Script 'Verify Supported Boot Modes'
This Build Plan can run on the target server, which is configured with UEFI optimization enabled and secure boot disabled.


Step 4 of 20: Run OGFS Script 'Boot'
Boot method: embedded
Agent is unreachable. Powering off server...
Configuring boot to Service OS: linux64
Rebooting the target server...


Step 5 of 20: Run OGFS Script 'Decommission Server'
The target server is not agent managed, skipping decommissioning


Step 6 of 20: Run OGFS Script 'Wait for HP SA Agent'
Sleeping for 3 minutes before checking for agent
Waiting for registration of agent running on maintenance OS
Failed To Wait for HP SA Agent: The agent did not appear on the network (is not listening on its port).
Additional information from boot control:
hpstartae copyright (c) 2011 hewlett packard - all rights reserved
/tmp/ae /
AE-test.xml
AutomationEngine
libcrypto.so
libcrypto.so.1.0.0
libcurl.so
libcurl.so.4
libcurl.so.4.2.0
libssh2.so
libssh2.so.1
libssh2.so.1.0.1
libssl.so
libssl.so.1.0.0
libz.so
libz.so.1
libz.so.1.2.5
README.TXT
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 1
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 2
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 3
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 4
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 5
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 6
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 7
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 8
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 9
ping: sendto: Network is unreachable
Network Interface is not up, test IP: 10.13.243.13, ping count: 10
Failed to download URL: http://127.0.0.1:8081/osprov_ogfs_agent-LINUX-SLES-11-X86_64
Response code received: 0
Possible reason: Couldn't connect to server
Error buffer: Failed to connect to 10.13.243.13: Network is unreachable
chmod: *: No such file or directory
HPSA OGFS Agent Setup
/tmp/post.bat: line 8: ./osprov/ogfs-agent-setup.sh: No such file or directory
HPSA OGFS Agent Start
/tmp/post.bat: line 10: ./osprov/ogfs-agent-start.sh: No such file or directory
Script exec failed: 127, reason:Key has expired
URI download failed, exiting
Automation Engine - version: 1.0.0

/opt/hp/hp-phoenix/scripts/ae.xml: loaded successfully


Wait for HP SA Agent failed with exit code 120.

Does anybody seen a similiar issue in the past or does someone know what the error code means?

I already configured the Intelligent Provisiong by hand with the above mentioned IP Address and i can ping it from the SA Core. But during the SA Deployment i cannot ping it!

We have alreday opened a service call at HPE, but we are trying and trying since three months anround that without any remarkable step forward!

Many thanks for your support and ideas in advance.

Warm Regards,

Frank

 

Wipe off those flip-flops it’s time to get out of the Sandbox.Open in a New Window

HPE&Docker.png

 

Innovators keep their fingers on the pulse of what’s next and for some time now they have had their sights on containers as the “next big thing”. Skeptics have been on the fence about this technology for a few years now. They have been saying things like, “it’s only for developers” and “it’s just a sandbox tool”. However, as a result of more and more production use cases coming up this year, containers are really getting out of the sandbox and into the building.

 sandboxIT.jpg

 

Players like Netflix™ and Uber™ have been pioneering this new technology, which makes sense because both are not only trend setters but also have created very disruptive technologies. If you’re looking for scale, fluid delivery, extremely fast upgrades and the ability to re-use effort throughout your organization—Containerization and Microservices are likely something you are looking at utilizing. Hewlett Packard Enterprise has been working very closely with Docker to help create our next generation of products. Not only can you use our HPE IT Operations Management Software tools to design and deploy containers-based services and their infrastructure for day one deployment,  we also empower you to monitor the health and compliance for those applications once placed out in the real world in day two and beyond.


On Wednesday, November 30th, 11am UK time, at HPE Discover London come hear Tom Goguen, VP and GM of R&D for ITOM, and Dan Powers, Head of Partner Technology Management at Docker, speak on where this technology is going next (Session ID: SL11392).

 

If by any chance you were not able to attend Discover this time, you can also watch the live stream of the The future belongs to the fast, transform your business with IT Operations Management session from anywhere in the world.

 

Want more info on this Discover session, check out this ITOM blog!

 

So let’s all grab our shovels and get to work.

If you are interested in more details about Hewlett Packard Enterprise and our view on containers feel free to comment below contact us.

 

Major issue DCAA / CSA PDTOpen in a New Window

Dears, 

we have DCAA 16.10 that has CSA 4.7 in the appliance , we have Vcenter Compute Capsule there we have edited it with some of our options there and renamed the flows . 

These Steps i have followed ,

  1. Deleted old Vcenter Compute Capsule from OO central.
  2. Package the new customized flows and created CP and deployed to central.
  3. Reconfigure Recourse offering with the New flows with that new CP .

The problem is that when checking the recourse offering again after i configure with the new flows it shows the path to old flows !! for example below i have configure the resource offering to point to that workflow 

That's the new Workflow: [/Library/CSA Content Pack/CSA3.2/Providers/Infrastructure/vCenter/MDD/MDD-vCenter Simple Compute - Validate Input Properties.xml]

checked Recourse offereing it change automatically to old one 

Old workflow [/Library/CSA Content Pack/CSA3.2/Providers/Infrastructure/vCenter/vCenter Clone Server/Validation/vCenter Simple Compute - Validate Input Properties]

My point how PDT working in DCAA!!

so after traking CSA.logs it showing that design trying to initi the old wworkflow which is not there as different UUID in OO central showing that error as following : 

15 Nov 2016 08:28:39,614 [pool-21-thread-20] ERROR [] ExecutorImpl : Error when executing process instance fc68a69aa69449dc996c97d93cdaf27f
java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 500 for URL: https://127.0.0.1:8443/PAS/services/rest/run_async/899ad185-7082-4a49-a070-bd54c20923f7?
at com.hp.csa.service.oo.OOExecutorDelegateImpl.run(OOExecutorDelegateImpl.java:90) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at sun.reflect.GeneratedMethodAccessor3316.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_60]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) ~[spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281) ~[spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at com.sun.proxy.$Proxy576.run(Unknown Source) ~[?:?]
at com.hp.csa.service.pluginframework.OOProcessEngineClient.executeAction(OOProcessEngineClient.java:42) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.pluginframework.PluginManagerImpl.invokeAction(PluginManagerImpl.java:54) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at sun.reflect.GeneratedMethodAccessor2955.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_60]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:201) ~[spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at com.sun.proxy.$Proxy521.invokeAction(Unknown Source) ~[?:?]
at com.hp.csa.service.process.ExecutorImpl.run(ExecutorImpl.java:73) [apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at sun.reflect.GeneratedMethodAccessor2639.invoke(Unknown Source) ~[?:?]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_60]
at java.lang.reflect.Method.invoke(Method.java:497) ~[?:1.8.0_60]
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317) [spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190) [spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) [spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99) [spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281) [spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) [spring-tx-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) [spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) [spring-aop-4.1.7.RELEASE.jar:4.1.7.RELEASE]
at com.sun.proxy.$Proxy737.run(Unknown Source) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_60]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_60]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://127.0.0.1:8443/PAS/services/rest/run_async/899ad185-7082-4a49-a070-bd54c20923f7?
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1839) ~[?:?]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1440) ~[?:?]
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) ~[?:?]
at com.hp.csa.service.oo.OORestClient.runFlow(OORestClient.java:280) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.oo.OORestClient.runFlowAsynchronously(OORestClient.java:163) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.oo.OOExecutorDelegateImpl.runFlow(OOExecutorDelegateImpl.java:225) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.oo.OOExecutorDelegateImpl.runOOFlow(OOExecutorDelegateImpl.java:163) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.oo.OOExecutorDelegateImpl.runOOFlow(OOExecutorDelegateImpl.java:140) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
at com.hp.csa.service.oo.OOExecutorDelegateImpl.run(OOExecutorDelegateImpl.java:87) ~[apis-04.70.000-SNAPSHOT.jar:04.70.000-SNAPSHOT]
... 36 more
15 Nov 2016 08:28:39,632 [pool-21-thread-20] ERROR [] ExecutorImpl : Error occured while executing process instance so Unlocking process Instance Id:fc68a69aa69449dc996c97d93cdaf27f
15 Nov 2016 08:28:49,698 [pool-28-thread-1] ERROR [] LifecycleLoggerImpl : [Lifecycle][Subscription Name : testvm10][RESOURCE_SUBSCRIPTION:Error:com.hp.csa.service.lifecycle.component.LifecycleActionFailedException: Action execution failed.

 

 

 

 

 

 

Error when installing McAfee antivirusOpen in a New Window

Hello!

We're trying to install the version 1.9.1.29107 of McAfee Antivirus For Linux, but when we make the installation, the system starts to use 100% of the CPU and then the whole system is unavailable. 

In the General Notes, I read that "Antivirus software is not supported on SA cores", but I don't know if that is the cause of the problem.

We are using the Express Version.

Do you have any idea why is this happening?

Thanks!

 

Product demo webinar: HPE Data Center AutomationOpen in a New Window

We’re excited to share a product demo webinar for HPE Data Center Automation (DCA). Learn how an Infrastructure Administrator, a Database Administrator and an IT Compliance Manager use the HPE Data Center Automation solution as part of their everyday jobs.

In this webinar, we will demo the solution for the following use cases:

  • Provision a server, in a matter of minutes
  • Patch a database, in a few simple steps with OOTB, repeatable workflows
  • Automate compliance, the smart way with OOTB content and automated scan & remediation

Click here to watch now!

The webinar is presented by Sibel Satiroglu, Senior Product Marketing Manager and Jason Odorizzi, Senior Technical Product Manager for Data Center Automation at Hewlett Packard Enterprise.

 

Got error while Scanning for unmanaged devicesOpen in a New Window

Hi All,

While scanning for unmanaged devices it throws below error message.. I have disabled the windows firewall from server manager and as well as I have disabled the firewall service but still no luck.... Manual install went ok without any issues..

 Error message string:

Exception:   com.opsware.ngui.adt.model.DeploymentHelperInitializationException

An error occurred while initializing Agent Deployment Helper in PRIMARYCORE-agents:

RemoteException occurred in server thread; nested exception is:

               java.rmi.RemoteException: EJB Exception: ; nested exception is:

               java.lang.RuntimeException: java.io.IOException:

 

Any Ideas....? Kindly help me on this issue

BR,

Raja

 

DCAA and Re-IP ???Open in a New Window

It's been a while since I've touched HPSA in general but really haven't dealt with DCAA yet.

I know that re-ip'ing a typical HPSA core is thin ice terriority and HPE PS and all that comes into play.  HOWEVER,:

1) Does using DCAA change this in any way ?

2) Is re-ip'ing a DCAA VM doable or do the same issue/restrictions still apply ?

Thanks any for information/direction on this question.

 

On-Demand Data Center Automation WebinarOpen in a New Window

 We’re excited to share a new on-demand webinar introducing HPE’s Data Center Automation solution, and we think there’s something in it for everyone.

Are you “everyone”?

Well, if you’re in a bit of frenzy about your data center, and you wish your IT operation costs were lower (or simply not spiraling out of control) or think it would be amazing if service requests didn’t take ages to fulfill, this webinar is for you. If you wish staying compliant didn’t have to be so difficult or you’d love if shadow IT could become a nonentity, this webinar is for you. And if you dream of the clouds, but have to deal with humdrum tasks instead, this webinar is for you!

In this webinar, you’ll hear about:

  • An overview of the Data Center Automation solution
  • What makes the solution unique
  • The business benefits (with real life examples)
  • How you can use the solution to scale (with flexibility and choice)

Click here to access the on-demand webinar.

From the webinar page, a pdf copy of the slides are also available to download.

 

 

 

 

 

 

Is DCAA 2016.1 a fully supported product?Open in a New Window

After playing around with dcaa 2016.1 and browsing the forums, I got the impression that nobody is using DCAA 2016 in mission critical environments.

The OVA as downloaded from hp does not install correctly, some strange iptable rules from hp are left on the device that prevent it from starting SA properly. This leaves the impression that nobody ever tested the release.

In our testenvironment the DCAA does strange DNS lookups to nonexisting domains that probably stem from the development environment.

6 months after release of 2016.1 I still cannot select the version when opening an SR.

DCAA 2016.1 is on SA 10.20 while the standalone product is on 10.23 with many rollup hotfixes. No hotfixes are available for DCAA(?). There is still no documented upgrade procedure from DCAA 1.0 to 2016.1 available.

Is anybody using DCAA in a missioncritical environment and if yes, what experience did you make?

Kind Regards

Erwin

 

When installing DCAA ,the command "opsware-sas start" can't preforn successfullyOpen in a New Window

    When installing DCAA that a trial version. When I preform the command that "/etc/init.d/opsware-sas  status ",I meet  a problem that " failed to peroform "startsync "  operation on Opsware SAS components

 

DCA - OVA file not prompting for Hostname, IPAddress, etcOpen in a New Window

Hi,

      I have downloaded the ova file and reassembled it as DCAA-1-0.OVA file.

When importing the OVA file in the VCenter client, it is not prompting for hostname, ipaddress, gateway, subnet-mask, etc.

I continue with this but after powering on it says hostname set as localhost.localdomain.

 

Am I doing anything wrong.

 

Breaking my head over this.

 

Appreciate your help.

 

Best Regards,

Sultan

 

Enhance your #HPDiscover experience!Open in a New Window

Enhance your #HPDiscover experience by joining #Vivit one day before #HPDiscover begins for the highly ranked #Vivit Deep Dive program – choose from one of the 10 sessions Register for these sessions through your new or existing #HPDiscover conference registration. http://bit.ly/I7Fbyo

 

Don’t miss out on #Vivit’s Deep Dive SessionsOpen in a New Window

Don’t miss out on #Vivit’s Deep Dive Sessions at #HPDiscover on Monday, June 1, from 1- 5pm.These sessions allow you to hear real-world implementation experiences and examples from practitioners who are in the field solving business problems with HP Software tools every day.  Cost per session is only $99 thanks to our sponsors--this is an incredible value which normally costs $495.  Register for these sessions through your new or existing #HPDiscover conference registration.
Learn more.
   http://bit.ly/I7Fbyo

 

Enhance your #HPDiscover experience by joining #Vivit!Open in a New Window

Enhance your #HPDiscover experience by joining #Vivit one day before #HPDiscover begins for the highly ranked #Vivit Deep Dive program – choose from one of the 10 sessions Register for these sessions through your new or existing #HPDiscover conference registration. http://bit.ly/I7Fbyo

 

"Turning the Dream of Rapid, Error-free Service Delivery into Reality" Vivit Webinar > May 27Open in a New Window

Join us on May 27 for "Turning the Dream of Rapid, Error-free Service Delivery into Reality" Vivit Webinar.

 

Register at:  https://www3.gotomeeting.com/island/webinar/registration.tmpl?id=249056162

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.