adurrant

Could be worth checking your detection methods, an application is only classed as successful, if after the install it's detected.

by the looks of it, network 4.5.2 is required? what version of net framework is on these machines to begin with? Try taking a look at these: http://fearthemonkey.co.uk/889/ http://www.nowmicro.com/deploying-net-framework-4-5-2-configmgr-application/

What windows OS are you attempting to deploy this to? It might be that you have to enable net framework 4.0 from within programs and features. Could use DISM for that.

Try execmgr.log and datatransfer logs

Hi there, Is there any issues when you try to install .net framework manually?

Hi there, Does your console version match the site version?

Bump

Hello all, I've ran into a few issues with SCCM 2012 R2 SP1, I have a remote 2 node SQL cluster, essentially one of the nodes failed a few months ago so it's been online for a while, during this time the SCCM DB was moved to this cluster, today the 2nd node is now online so I was expecting that SCCM was install what it needed on this server, I am however running into issues with SCCM thinking that a drive of E:\ exists in the sitecomp.log however this drive does not exist on the node, is there anyway of changing the path? or will I need to reset my SQL configuration again from the setup? Sitecomp log: Thread "SiteComp server polling Thread #1" id:2808 terminated normally $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.811-60><thread=2808 (0xAF8)> The server already contains some of the required files for this component. A disk space check will not be made. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.831-60><thread=2736 (0xAB0)> A network connection already exists to \\NAK-PG-CSQL1B\ADMIN$. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.831-60><thread=2736 (0xAB0)> ~Cannot create \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64, [error code: 67, error message: The network name cannot be found.]. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.837-60><thread=2736 (0xAB0)> Could not copy file C:\Program Files\Microsoft Configuration Manager\bin\x64\smssqlbkup.exe to \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64\smssqlbkup.exe: Could not create directory \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64. The operating system reported error 0: The operation completed successfully.~~ $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.838-60><thread=2736 (0xAB0)> INFO: 'NAK-PG-CSQL1B' is not a valid FQDN because the format is invalid. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.838-60><thread=2736 (0xAB0)> A network connection already exists to \\NAK-PG-CSQL1B\ADMIN$. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.861-60><thread=2736 (0xAB0)> Component SMS_MP_FILE_DISPATCH_MANAGER is running. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.864-60><thread=9672 (0x25C8)> ~Cannot create \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64, [error code: 67, error message: The network name cannot be found.]. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.865-60><thread=2736 (0xAB0)> Could not copy file C:\Program Files\Microsoft Configuration Manager\bin\x64\srvboot.exe to \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64\srvboot.exe: Could not create directory \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64. The operating system reported error 0: The operation completed successfully.~~ $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.865-60><thread=2736 (0xAB0)> INFO: 'NAK-PG-CSQL1B' is not a valid FQDN because the format is invalid. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.866-60><thread=2736 (0xAB0)> A network connection already exists to \\NAK-PG-CSQL1B\ADMIN$. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.892-60><thread=2736 (0xAB0)> ~Cannot create \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64, [error code: 67, error message: The network name cannot be found.]. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.897-60><thread=2736 (0xAB0)> Could not copy file C:\Program Files\Microsoft Configuration Manager\bin\x64\checkspn.exe to \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64\checkspn.exe: Could not create directory \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64. The operating system reported error 0: The operation completed successfully.~~ $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.897-60><thread=2736 (0xAB0)> INFO: 'NAK-PG-CSQL1B' is not a valid FQDN because the format is invalid. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.898-60><thread=2736 (0xAB0)> A network connection already exists to \\NAK-PG-CSQL1B\ADMIN$. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.918-60><thread=2736 (0xAB0)> ~Cannot create \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64, [error code: 67, error message: The network name cannot be found.]. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.923-60><thread=2736 (0xAB0)> Could not copy file C:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe to \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64\vcredist_x64.exe: Could not create directory \\NAK-PG-CSQL1B\E$\SMS_NAK-PG-SCCM01.NAK.CO.UK\bin\x64. The operating system reported error 0: The operation completed successfully.~~ $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.923-60><thread=2736 (0xAB0)> INFO: 'NAK-PG-CSQL1B' is not a valid FQDN because the format is invalid. $$<SMS_SITE_COMPONENT_MANAGER><10-07-2015 10:59:00.923-60><thread=2736 (0xAB0)> There is no E:\ Drive on NAK-PG-CSQLB Any ideas?

Hey Dude, This my first post, I think this is an awesome guide! however, following the deployment of the endpoint client to my workstations\servers, I have noticed that the endpoint client, disabled remote desktop through the firewall, I have looked through the firewall policies on config manager and can't find anything, so I can allow this, it's going to be a nightmare opening all that up on all workstations, is there not a way where the endpoint protection uses the same config as previous (e.g. current rules on windows firewall) any help? Cheers, Alex.