Securing Active Directory integration
-
All is well with the world now! Had to revert to Visual Studio 2008 Professional on a Windows 7 32 bit box.
-
Did anyone ever find a resolution for this? I have the exact same config as the OP but no access to a Pro version of Visual Studio. I have the exact same error.
-
Did you try the Express version of 2008?
I don’t know if the Express version will work, but it’s worth a try. I think you’ll need the C# package.
-
I downloaded Visual Studio Express 2008 Visual C# Edition and tried to go through the steps in the wiki. I was stopped when trying to build the Fog Service Installer project. Evidently, VS 2008 Exp. Ed. doesn’t like .vdproj files and won’t proceed.
-
I have the same problem with Visual Studio Express 2008 Visual C# and Visual Studio Express 2010 Visual C# that they don’t like the .vdproj file in the fog service folder. Thus meaning I cannot complete the walk through on the wiki pages to securing active directory integration please can any one help to fix this error so that I can change the default passkey.
-
This post is deleted! -
I have not found a way to build the installer, but you could simply replace the hostnamechanger.dll file in your sysprep’d image from the first part of the tutorial after you generate the new hostnamechanger.dll. I have not had a chance to test this as of yet. If anyone has a moment please let me know how you make out.
-
[quote=“Jordan Rumph, post: 4527, member: 1473”]Did anyone ever find a resolution for this? I have the exact same config as the OP but no access to a Pro version of Visual Studio. I have the exact same error.[/quote]
There are ‘issues’ with mixing and matching .net dependencies on Windows 7 to begin with and they have to be installed/slipstreamed in the order they are released. 1.0 --> 2.0 --> 3.0 --> 3.5 --> 4.0
If you go into Event Viewer you should see a bunch of WMI warnings and errors. For some unknown reason 7 will unregister the wrong DLL’s if the staged deployment of .Net updates isn’t followed in the order they are given. You can attempt to repair WMI, but it’s usually safest if you just wipe and rebuild.
Build your baseline first
- OS, fixes and patch level to X date
- Then worry about applications after.
Ryans VM has some excellent guides on the subject and his method works will all available deployment platforms to build a solid and fast OS baseline for XP, Vista and 7.
[url]http://siginetsoftware.com/forum/forumdisplay.php?9-RyanVM-Integrator[/url]
-
I"m having issues compiling the fog service installer. Has anyone had any success with this? Also curious if it is better to move/copy the hostnamechange.sln to the host system? Thanks in advance
-
I just ran into this issue trying to compile with Visual Studio 2013. In 2011 MS announced they would not longer support Visual Studio Installer Projects in future VS versions. However, due to rather loud customer feedback they ended up created an extension that could open those projects.
[url]http://blogs.msdn.com/b/buckh/archive/2011/03/17/visual-studio-setup-projects-vdproj-will-not-ship-with-future-versions-of-vs.aspx[/url]
[url]http://blogs.msdn.com/b/visualstudio/archive/2014/04/17/visual-studio-installer-projects-extension.aspx[/url]
[url]https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d[/url]I’ve installed the extension and tested it out with VS 2013 Pro and it works great. The FOG service installer project loads and compiles successfully. I didn’t test it with the Express version so I can’t confirm if everything is OK in that environment, but at least it is possible.
Edit: Forgot to mention, I also received the build error with blank.jpg. I simply deleted the reference from the solution explorer and then rebuilt the solution. Everything built correctly. The jpg was likely being used as a graphic in the installer, but is not likely to be critical. The newly built service installed with no issues.
-
This post is deleted!