In addition to this procedure, is it also necessary to use command prompt as administrator to delete the trigger of Function Discovery Resource Publication by typing:
sc triggerinfo FDResPub delete ?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
In Win10, v 1809 I go to "Network" in file explorer and no computers are showing - neither my computer nor other computers on the network.
I was able to find the ip address of the computer I was searching for and successfully ping it via command prompt.
Any ideas?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
In addition to this procedure, is it also necessary to use command prompt as administrator to delete the trigger of Function Discovery Resource Publication by typing:
sc triggerinfo FDResPub delete ?
I didn't and I just added the task to the scheduler. I guess discovery goes on then off then back on.
Hey galileo1564, you seem to have a good understanding of this situation. Your response was in reply to this statement in the previous post:
> To add the trigger, run as Administrator:
> sc triggerinfo FDResPub start/strcustom/fbcfac3f-8460-419f-8e48-1f0b49cdb85e
> /PROFILE_CHANGED_TO_PRIVATE
I'm trying to get a better understanding of what is happening here.
What are the actual circumstances that will cause this trigger to activate?
What does the statement "/PROFILE_CHANGED_TO_PRIVATE" actually mean?
To me, (and I'm not a programmer, just a self-taught computer geek with an MS in EE) this doesn't look like a piece of programming syntax that I recognize as fitting with some programming language. It strikes me as more like a comment or placeholder, as though the coder was leaving a reminder for himself to come back and put in the right code when he figured out what that was.
What's your take on this? Thanks!
If this is correct, and it looks to me like it probably is, my interpretation is that the only time the trigger is activated is if the network has first been set to public and then the setting is changed to private.
I have all my systems set to private as the default setting, so in the normal course of events I would never be *changing* it to private. Wouldn't this mean the event would never be triggered? Instead of PROFILE_CHANGED_TO_PRIVATE, I would think PROFILE_IS_SET_TO_PRIVATE is what might be needed here.