Our application has Forms Authentication with pool identity ASPNET user. Hi, we are doing a POC on Intune and Azure with some hybrid joined machines and are having a ton of issues getting win32 apps deployed. NET 4. Oct 18, 2012 · It works well if the user enters correct username and password, but in case username or password is wrong, LogonUserA always returns a same error code 1008 that translate to a vague message "An attempt was made to reference a token that does not exist. The registry location for win32 apps: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Win32Apps\. MDM ConfigurationManager: Command failure status. May 20, 2022 · Intune Win32 App Issues Troubleshooting Client-Side Process Flow 1 Intune Management Extension The Intune management extension is the client-side component to manage the MDM Intune Win 32 application deployment. The machine is co-managed with SCCM. They will fix it soon probably, but if you don`t want to wait, you should try alternate upgrade server. Excel Repair. a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 104. When LogonUser is called with LOGON32_LOGON_NEW_CREDENTIALS it returns a token that is a clone of the current token. MoveNext (). Get the Intune Win32 Content Prep Tool and run it. The Intune Management Extension logs give me the following errors: <! [LOG [ [Win32App] Set EnforcementStateMessage EnforcementState: Error, ErrorCode. Nov 24, 2019 · Enforcement action failed due to error, will retry immediately. NVIDIA GeForce GTX 1600x Super. exe in the search results and then select Run as. config: The binary which runs the health check. Click iCloud in the sidebar. Click on Start; then click on All Programs. Click Apple ID. TokenAquireException: Attempt to get token, but failed. The first four bytes (DWORD) of the Data section contains the error code. Win32 apps log location: Win32 Agent logs on the client machine are located at “ C:\ProgramData\Microsoft\IntuneManagementExtension\Logs”. The policy is named "Allow to log on locally" and in my Win Server 2008 R2 domain, I have for domain controllers: BUILTIN\Print Operators, BUILTIN\Server Operators, BUILTIN\Account Operators, BUILTIN\Backup Operators, BUILTIN\Administrators. Error code 0x80004005 most commonly occurs when a computer’s registry or essential files become corrupted. Aug 19, 2021 · [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). It took us a while to figure out that the intune connector installer (msi file) was getting blocked by our network. Now press the Add button. There are a variety of reasons this could be occurring. LogonUser failed for svc-LocalAgent$. Try restart your PC and then run Windows Update again. Jan 14, 2020 · Hi, we are doing a POC on Intune and Azure with some hybrid joined machines and are having a ton of issues getting win32 apps deployed. Repair corrupt Excel files and recover all the data with 100% integrity. No reason given. In most cases restarting the computer will fix the unknown errors. Restart Your Computer Restarting your computer fixes a large number of problems, and there is a reason why restarting is the first way to fix the IT world. It will scan your system files and to repair missing or corrupted system files in Windows. Click Apple ID. The setup process for the MSI failed With that in mind, if you find yourself in this situation the first thing to do is check whether the MSI has been downloaded. in windows 2000 for running logonuser api we need SE_TCB_NAME Privilege (act as part of operating system). exe and ClientHealthEval. Execute the following command. - Nicholas Blumhardt Jan 22, 2014 at 2:18 4 I had the same issue impersonating against a different domain than the one my application ran in. The return code 1008 means that the session is idle or the session ID is 0. dll" failed. 0, windows xp pro sp2 pl (polish) Some install actions often fail with error: "[DAU] [Error 1008 Calling LoadUserProfile. it is really annoying and counter-productive to my work at times when I. The registry location for win32 apps: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Win32Apps\. h header defines LogonUseras an alias which automatically selects the ANSI or Unicode version of this function based on the definition of the UNICODE preprocessor constant. userName, domain an password need to be passed as Windows Wide. Aug 19, 2021 · [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). 55495, compareVersion: 5. 1795 (0x703). The winbase. Shift + F10 -> eventvwr. " I have no idea what that equates to in this context although the message in the log says " AAD. UHF - Header. UHF - Header. The setup process for the MSI failed With that in mind, if you find yourself in this situation the first thing to do is check whether the MSI has been downloaded. The issue you are encountering is that you are specifying a username and password which is only recognized on the . Click on Start; then click on All Programs. SYSmark 2014 v1. log—>This is the main client log file, it contains all the agent check-in, compliance status, enforcement status, policy request, policy processing, and reporting activities. Helloo Hersheykiss. Here is the code that fails for me: // Copy password to unmanaged memory and get pointer to it IntPtr passwordPtr = Marshal. In most cases restarting the computer will fix the unknown errors. Right click on Command Prompt and run as administrator. For any win32 app that gets deployed on a device, there is a registry location that stores the information about the app with its deployment status. I understand your concern, and we in Community will try to help you in the best possible way we can. Under Computer name, domain, and workgroup settings, click. 0, windows xp pro sp2 pl (polish) Some install actions often fail with error: "[DAU] [Error 1008 Calling LoadUserProfile. Aug 19, 2021 · [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). Win32Exception (0x80004005): An attempt was made to reference a token that does not exist. Event Xml:. 1794 (0x702) The redirector is in use and cannot be unloaded. In the User Accounts window, click LogMeInRemoteUser one time so that it is highlighted. 24 Nov 2019. 1792 (0x700) An attempt was made to logon, but the network logon service was not started. Learn how your comment data is processed. Event ID: 1008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Eduardo-PC Description: The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl. Click Next. It works well if the user enters correct username and password, but in case user. There's some stuff missing but the following code seems to do the trick. Win32 App that isnt working command powershell. 1 I'm struggling with a problematic drive mapping user preference where I'm trying to use the user's %LogonUser% variable to a network location (eg. If familiar with ConfigMgr and the ConfigMgr agent, there we have the same concept. First published on TechNet on May 15, 2018 **Edit** Here's some formal docs guidance on troubleshooting app install errors, and a list of known error. On your drive map preference properties, press F3 then check whether "Resolve Variable" option is selected. Run CHKDSK Check Disk is the first step to diagnosing your Windows computer. NET 4. It is suggested to try to restart the device and check if the Powershell script deployment is successful. The LogonUser function attempts to log a user on to the local computer. It took us a while to figure out that the intune connector installer (msi file) was getting blocked by our network. Click on Accessori. I understand your concern, and we in Community will try to help you in the best possible way we can. js ao. Sep 19, 2015 · Event ID: 1008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Eduardo-PC Description: The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl. Format ("LogonUser failed with error code : {0}", ret) Throw New ApplicationException (strErr, Nothing) End If Dim retVal As Boolean = SecuUtil32. Hi, we are doing a POC on Intune and Azure with some hybrid joined machines and are having a ton of issues getting win32 apps deployed. Press Run, and input the following command "services. More Tools. The first four bytes (DWORD) of the Data section contains the error code. Downloaded MSI packages are stored in C:\Windows\System32\config\systemprofile\AppData\Local\mdm so take a look in there and see if you can find your MSI. Jan 14, 2020 · Hi, we are doing a POC on Intune and Azure with some hybrid joined machines and are having a ton of issues getting win32 apps deployed. Methods to fix the error 1008 1. Jan 14, 2020 · Hi, we are doing a POC on Intune and Azure with some hybrid joined machines and are having a ton of issues getting win32 apps deployed. Nov 24, 2019 · Enforcement action failed due to error, will retry immediately. This site uses Akismet to reduce spam. Click Apple ID. Right click on the Assetto Corsa game on the left and open the Features tab. 程序员秘密 程序员秘密，程序员秘密技术文章，程序员秘密博客论坛. Win32Exception (0x80004005): An attempt was made to reference a token that does not exist. 0 web application that running on IIS7/Win2008. 29 Sep 2022. For example, the application is executed in the following way: iedoz. Below are the 3 Intune Management Extension Agen t working folders. 1786 (0x6FA) The workstation. System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. It works well if the user enters correct username and password, but in case user. js ao. - Nicholas Blumhardt Jan 22, 2014 at 2:18 4 I had the same issue impersonating against a different domain than the one my application ran in. No solutions agaian :- ( The problem is why am i getting 3 diff errors for same function. Downloaded MSI packages are stored in C:\Windows\System32\config\systemprofile\AppData\Local\mdm so take a look in there and see if you can find your MSI. Restart Your Computer Restarting your computer fixes a large number of problems, and there is a reason why restarting is the first way to fix the IT world. But the script is not getting executed and I find out that IME (Intune management extension" service is not installed on the devices. Once you remove all the traces of the existing installation of a program, try re-registering the following dll file. LogonUser failed with error code : 1008 AAD User check is failed, exception is System. To resolve this issue, use one or more of the following methods: Click Start, right-click Computer, and then click Properties. Set SidecarReady: True with IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) Successfully get the token with client id fc0f3af4-6835-4174-b806-f7db311fd2f3 and resource id 26a4ae64-5862-427f-a9b0-044e62572a4f IntuneManagementExtension 20/08/2021 10:32:30 19 (0x0013). Choose LogOnAsABatchJob, and then select the Add User or Group button. CloseHandle (tokenHandle). Methods to fix the error 1008 1. Choose LogOnAsABatchJob, and then select the Add User or Group button. The winbase. Error code: -2147023293 Error description: Fatal error during installation After using the Windows upgrade tool (fresh start) in the Windows Defender Security Center and then scanning it, a fatal error is written: Protection definition update failed. The return code 1008 means that the session is idle or the session ID is 0. Win32Exception (0x80004005): An attempt was made to reference. Nov 24, 2019 · Win32 apps log location: Win32 Agent logs on the client machine are located at “ C:\ProgramData\Microsoft\IntuneManagementExtension\Logs”. INTUNEWIN app package at a deeper level. 0 web application that running on IIS7/Win2008. Environment: Zenworks 10. We see status Failed even if we successfully installed the app. Method 1: I would suggest you to run System File Checker. 6002: App install is blocked on the machine due to a pending hard reboot. We will go through the purpose of these folders in detail. In most cases restarting the computer will fix the unknown errors. " Of course, if LogonUserA failed then there'll be no valid token, so what does this error mean?. I did some test, in my test environment variable "logonuser" works as expected. In the event logs (Admin) for "DeviceManagement-Enterprise-Diagnosti-Provider", i found the below error:-. The machine in question is running Build 2004 and has been signed into before. Downloaded MSI packages are stored in C:\Windows\System32\config\systemprofile\AppData\Local\mdm so take a look in there and see if you can find your MSI. Set SidecarReady: True with IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) Successfully get the token with client id fc0f3af4-6835-4174-b806-f7db311fd2f3 and resource id 26a4ae64-5862-427f-a9b0-044e62572a4f IntuneManagementExtension 20/08/2021 10:32:30 19 (0x0013). This will open the "Local Services" window. All Win32App has been added. The setup process for the MSI failed With that in mind, if you find yourself in this situation the first thing to do is check whether the MSI has been downloaded. Enter gpedit. Excel Repair. Error code: -2147023293 Error description: Fatal error during installation After using the Windows upgrade tool (fresh start) in the Windows Defender Security Center and then scanning it, a fatal error is written: Protection definition update failed. NET 4. dll" failed. There doesn't appear to the a way of controlling this step (as you would expect). Right click the. I'm using LogonUserA function to authenticate a user in an ASP. Event ID: 1008 Task Category: None Level: Warning Keywords: User: DURAND-PC\Arthur Durand Computer: Durand-PC Description: The Open procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl. The ultimate action-packed science and technology magazine bursting with exciting information about the universe; Subscribe today for our Black Frida offer - Save up to 50%. 0 web application that running on IIS7/Win2008. In the password screen set a password that is at least 8 characters long, letters or numbers, keeping in mind that it is case sensitive. System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. com and delete the serial number of the device 2. Now press the Add button. It works well if the user enters correct username and password, but in case user. msc to open the Local Group Policy Editor window. Open a command prompt window. To resolve this issue, use one or more of the following methods: Click Start, right-click Computer, and then click Properties. Press Run, and input the following command "services. Error code 0x80004005 most commonly occurs when a computer’s registry or essential files become corrupted. exe and ClientHealthEval. UHF - Header. We use. Aug 19, 2021 · [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). We see status Failed even if we successfully installed the app. ]" in the zenworks. Oct 18, 2012 · It works well if the user enters correct username and password, but in case username or password is wrong, LogonUserA always returns a same error code 1008 that translate to a vague message "An attempt was made to reference a token that does not exist. Click AppleID. A magnifying glass. 5 Agu 2019. Click on Accessori. Select the Domain option, and then type the domain name in the Domain dialog box to add the computer back to the domain. config: The binary which runs the health check. [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). Method 1: I would suggest you to run System File Checker. We've just started to look at automating out Window AMI's however hit the same error regardless of the build components/tests that are make up the pipeline. Click on Accessories. [Win32App] ESP starts checker for valid AAD user token after all device policies created IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker starts IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005) [Win32App] BackgroundWorker ends IntuneManagementExtension 20/08/2021 10:32:30 5 (0x0005). 7862197" date="10-18-2022" component="IntuneManagementExtension" context="" type="3" thread="5" file=""> <!. TokenAquireException: Attempt to get token, but failed. 6001, App . To run the SFC scan, refer to the Microsoft article below. DuplicateToken (tokenHandle, SecurityImpersonation, dupeTokenHandle) If False = retVal Then SecuUtil32. " I have no idea what that equates to in this context although the message in the log says "AAD User check using device check in app is failed". In the app Device status on one of the tests (Greenshot) I can see that it has failed twice (it ha failed more than that, but its a start) and they both have 0x80070002 as the status details. The winbase. 1385 = Logon failure: the user has not been granted the requested logon type at this computer. Nov 24, 2019 · Win32 apps log location: Win32 Agent logs on the client machine are located at “ C:\ProgramData\Microsoft\IntuneManagementExtension\Logs”. No reason given. UHF - Header. 1385 = Logon failure: the user has not been granted the requested logon type at this computer. Get the Intune Win32 Content Prep Tool and run it. On a side note here, everything you have configured in your SCCM GPO is bad or meaningless in a ConfigMgr context as you should always disable automatic updates to prevent the WUA from doing things on its own like rebooting systems and you should never set a WSUS server as this may override ConfigMgr's local group policy and cause the agent to disable software update completely. Click on Start; then click on All Programs. optima health grocery catalog
But the script is not getting executed and I find out that IME (Intune management extension" service is not installed on the devices. . Win32app logonuser failed with error code 1008
NET 4. It's possible xp_cmdshell is executed through the proxy account. You cannot use LogonUser to log on to a remote computer. LogonUser failed with error code : 1008 AAD User check is failed, exception is System. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. Choose Apple menu > System Preferences. PROBLEM SUMMARY: The WTSQueryUserToken function is used for getting the logon user credentials to automatically start the node with that user's privileges. Instead of using an impersonated method call and running your function in WindowsImpersonationContext, you can use RunImpersonated (SafeAccessTokenHandle, Action) and provide your function directly as a parameter. The return code 1008 means that the session is idle or the session ID is 0. Oct 18, 2012 · I'm using LogonUserA function to authenticate a user in an ASP. Please try that. Select the Workgroup option, and then type a workgroup in the Workgroup dialog box. Jun 12, 2020 · To troubleshoot Win32 app issue, you need to check the log files located at: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs. js ao. Method 1: I would suggest you to run System File Checker. Click on Start; then click on All Programs. In the application I first impersonate to another user using the LogonUser and ImpersonateLoggedOnUser WIN32 APIs, and then I'm trying to check If for a given user name and password, if the authentication succeed. Sep 19, 2015 · Event ID: 1008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Eduardo-PC Description: The Open Procedure for service "WmiApRpl" in DLL "C:\WINDOWS\system32\wbem\wmiaprpl. Dec 11, 2019 · Error code 1008 = "An attempt was made to reference a token that does not exist. Within the Win32 app prerequisites script you can specify which data type from the PowerShell output. The health check involves 4 files: ClientHealthEval. Sep 19, 2015 · I understand your concern, and we in Community will try to help you in the best possible way we can. Oct 18, 2012 · I'm using LogonUserA function to authenticate a user in an ASP. We use authenticated user and password to access a network SQL server with windows integrated security. Click Apple ID. System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Format ("LogonUser failed with error code : {0}", ret) Throw New ApplicationException (strErr, Nothing) End If Dim retVal As Boolean = SecuUtil32. Went through and set them up as allowed installs to my IT security group. Win32Exception (0x80004005): An attempt was made to reference a token that does not exist AAD User check using device check in app is failed, now fallback to the Graph audience. 6001: App install is blocked because one or more of the app's dependencies failed to install. Get the Intune Win32 Content Prep Tool and run it. Error code 0x80004005 most commonly occurs when a computer’s registry or essential files become corrupted. Data supplied is of wrong type. we unblocked that and now it's getting installed when we push a win32 app via intune, but the application we are trying to push (powershell. ee, including cookie policy. LogonUser failed for svc-LocalAgent$. we unblocked that and now it's getting installed when we push a win32 app via intune, but the application we are trying to push (powershell. zg ww. 20 Mei 2022. All Win32App has been added. Event Xml:. Get the Intune Win32 Content Prep Tool and run it. It's possible xp_cmdshell is executed through the proxy account. Intune Management Extension - Get to know the. System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. There are a variety of reasons this could be occurring. Method 1: I would suggest you to run System File Checker. In the registry key, you will see multiple SID’s either for device or user. Hi, Im trying to programmatically authenticate a user against NT under windows 2000. The setup process for the MSI failed With that in mind, if you find yourself in this situation the first thing to do is check whether the MSI has been downloaded. About Press Copyright Contact us Creators Advertise Developers Terms Privacy Policy & Safety How YouTube works Test new features Press Copyright Contact us Creators. I think the problem is with BD update server. – As you can see it has been added before. Win32Exception (0x80004005): An attempt was made to reference a token that does not exist AAD User check using device check in app is failed, now fallback to the Graph audience. Win32Exception (0x80004005): An attempt was made to reference a token that does not exist at Microsoft. It should use the user name in the call to NetUserChangePassword, along with the password it tried as the old password. 1792 (0x700) An attempt was made to logon, but the network logon service was not started. LogonUser failed with error code : 1008 AAD User check is failed, exception is System. ) NOTE: Returns only when presented with valid username and password/credential. Try run Windows Update and see whether you are able to update windows. I tested it on simple executable, and it works. , username, password) at the time of the call. PROBLEM SUMMARY: The WTSQueryUserToken function is used for getting the logon user credentials to automatically start the node with that user's privileges. Photo Repair. This site uses Akismet to reduce spam. we unblocked that and now it's getting installed when we push a win32 app via intune, but the application we are trying to push (powershell. Oct 18, 2012 · I'm using LogonUserA function to authenticate a user in an ASP. Method 1: I would suggest you to run System File Checker. dll" failed with error code The device is not ready. After installing Link Tracking to the SharePoint farm, in Central Administration if you select the Authentication option for 'Windows 4294386, WORKAROUND:Either grant the user. UHF - Header. Exception: Microsoft. The setup process for the MSI failed With that in mind, if you find yourself in this situation the first thing to do is check whether the MSI has been downloaded. I understand your concern, and we in Community will try to help you in the best possible way we can. in windows 2000 for running logonuser api we need SE_TCB_NAME Privilege (act as part of operating system). Event Xml:. 6001: App install is blocked because one or more of the app's dependencies failed to install. Click on Start; then click on All Programs. Downloaded MSI packages are stored in C:\Windows\System32\config\systemprofile\AppData\Local\mdm so take a look in there and see if you can find your MSI. Jun 12, 2020 · To troubleshoot Win32 app issue, you need to check the log files located at: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs. Intune Win32 App Issues Troubleshooting Client-Side Process Flow 1 Intune Management Extension The Intune management extension is the client-side component to manage the MDM Intune Win 32 application deployment. logonuser failedwith error code 1008The first four bytes (DWORD) of the Data section contains the error code" and wish to solve that. Administrative Tools>Local Security Settings>Local Policies>User Rights Assignment, right-click on Access this computer from the network>Properties>Add Users or Groups, add everyone if not added before. MoveNext (). i need to set the SE_TCB_NAME Privilege programatically with out. Detection can be based on Registry, MSI Product code, or File Path as configured while creating the app in Intune portal. Logonuser api is working fine in windowsXp,Windows2003 server. we unblocked that and now it's getting installed when we push a win32 app via intune, but the application we are trying to push (powershell. PROBLEM SUMMARY: The WTSQueryUserToken function is used for getting the logon user credentials to automatically start the node with that user's privileges. in windows 2000 for running logonuser api we need SE_TCB_NAME Privilege (act as part of operating system). json: The json report with results of the rules defined by the xml. a connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 104. 1330 - ERROR_PASSWORD_EXPIRED (Logon failure: the specified account password has expired. using System; using System. Click the Computer Name tab, and then click Change. Please follow the steps introduced in the guide by clicking the link as below. LOGON32_PROVIDER_WINNT50, I get the return code 1348. All Win32App has been added. NVIDIA GeForce GTX 1600x Super. The registry location for win32 apps: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Win32Apps\. . craigslist mobile pets, wjz 13 news baltimore, frosthaven differences, squirt korea, amazon 6 page memo reddit, shoe nami, estadisticas de la mlb, jenni rivera sex tape, autism creature picrew, bdsm insex, scout69 com, mccolly real estate co8rr