Quote: Originally Posted by Dvanmeter If you are getting errors on the installation it may be because you are using a strong password when connecting throught ntlm to the database. I ran into this also. Mcafee confirmed this to be true in the last beta and says it wont be fixed until a service pack is released.
is there any more information that you, or McAfee has on this? I am mainly looking for a 'definition' of a strong password in this case.
The problem with the installation where it looks like it is complete then rolls back is due to an issue with strong passwords. Mcafee defined it as a password with !@#$%^ type symbols. The work around was to set it to use sa password to the database on the install, when the installation is complete then you can change it back to use ntlm authentication and it wont have a problem with the special characters. This problem did not seem to exist as far as I remember in beta 2 of EPO 4 but appeared in beta 3 and the final product.
The password thing was enough of an issue that if you had read the epo 4.0 readme.html that comes with the software you would have found it in the list of possible problems you are likely to experience together with workaround instructions.
Using extended or double-byte characters in the global administrator or database user name or password might prevent the software from installing successfully. To workaround this issue, install the software using a Domain User that has a “simple” password. After the installation, log on to the ePO server, go to https://<SERVER>:8443/core/config, change the credentials to a User Account with a “complex” password, then restart the ePO services.
I went to infosec yesterday and spoke to one of the chaps i have seen before, i asked him about the beta and how to set it to deploy, we went through it and i saw the art of getting it to work. tried the same today on my spare box, and guess what ? - yep its still not working properly. hate to be so dismissive, but i am sticking with 3.6 until this gets sorted out, it may look pretty but IMO just isnt as logical or as easy to work with. sorry guys
RSD Gone, then how did I just install the RSD 2.0 in EPO 4 a couple of days ago. I dont know who you talked to but they are wrong. I was on the prepublic beta team for the last several months and they just posted patch 2 and with rsd 2.0 a few days ago.
Aztech.. dont know where you got your info from but as the last poster said
you are totally wrong.
RSD 2.0 is finally out of BETA and is on general release through the grant number accessable area of the downloads (bottom option in the EPO 4.00 downloads subsection) (NB you will need to install EPO patch 2 first)
Personally I dont find it as easy to automate as the 3.6.1 version, but there are some nice features too