If I were designing the whole system from the ground up, I wouldn’t do this either – but what is your reason?

You are absolutely correct, sir! I mistakenly wrote that the “git commit” was to update GitHub; it just updates the local repository. And a “git push” back to GitHub is not necessary here. I will correct the post. Thanks for catching that!

I would agree with that solution – if that works for you on a particular app, then certainly do that instead. However, this was the only solution that worked in my case.

Hah! Ironically by adding the < a > tag in my comment it actually made a link.

I agree with you, Railo is stricter but I seriously regard the ability to add a space between the < and “cftag” a bug . (security implications abound too)

I’m not sure I understand your question; the issue is that Railo (at least the older versions – can’t speak for >3.2.1) is not as forgiving as CF is with CFML tags. I had several CFML apps and had to alter some of the tags that were mistyped to make the site render properly. Regular HTML and XML would be rendered by IIS anyway, so no changes were necessary there.

Thanks, David. In our case, our 2008 DCs were 32-bit, so in-place upgrades were not an opton. We built a new virtual machine with 2012, which automatically extended the AD schema as part of the promotion processes. Once all FSMOs and services are migrated from the legacy DCs, we’ll demote them and raise the forest and domain functional levels.

D.

It did not upgrade it automatically in my case; I was required to do the above in order to upgrade 2008 to 2012.

It helped me so so so much .!!

Thanks

Anthony,
I have tried what worked for you but get the following ERROR:
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

Any ideas?

Marius

I figured it out. I was trying to change the hard-coded connection string in my devexpress xtrareports. I was able to change the connection dynamically on Page Load of my xtrareport. as shown below.

Me.myTableAdapted.Connection = New Data.SqlClient.SqlConnection(ConfigurationManager.ConnectionStrings(Session(“myConnStr”)).ToString)

Thank you again for the excellent article!

Thanks,
Anthony

I’m not sure I understand what you’re asking, but if you’re talking about including it in the markup (.aspx file), you can replace the hard-coded connection string in an ASP:SqlDataSource tag as in http://satindersinght.blogspot.com/2012/01/how-to-set-dynamic-connectionstring-of.html.

…

Yes, that’s correct.

Okay so after I run the Schema updater on my server I would update the operating system its self like I would upgrade from Windows XP to Windows 7?

My understanding is that it would be the latter, as the forest would already be upgraded. I have not done this in a production environment where there are multiple DCs, but it seems that it would be unnecessary to upgrade the forest more than once. However, running the command on the secondary DC shouldn’t cause any problems, since the forest will already be prepared.