User Support Forum

I just networked a computer at the Church but I get a message that the software does not have a digital signature. If I tell it to run anyway it works fine. I installed the netsetup off the PC that PC+ is installed on. Is this my mistake? Should I have run the netsetup off the original CD? or is there something else wrong?

tborgal wrote:I just networked a computer at the Church but I get a message that the software does not have a digital signature. If I tell it to run anyway it works fine. I installed the netsetup off the PC that PC+ is installed on. Is this my mistake? Should I have run the netsetup off the original CD? or is there something else wrong?

I'm assuming by "the PC that PC+ is setup on" that you're talking about the 'server' machine. This is the normal way to run NetsetupX (where X is the PC+ version you have). Is this a Window's notice ?? FWIW ... it sounds like something did not update in the local computer's registry.

Neil,
Your assumptions are correct. It is a Windows notice. Both machines are running XP Professional, and I am running PC+ V10. I have not looked at the original CD but I assume that the netsetup10 file is on it not compressed. The thing I did was to open the folder on the server machine from the networked laptop and run the file from it. I did not use the original CD, should I have.

The warning that you are receiving is related to Internet Explorer 7. I think it has been installing recently through Windows Update. This is yet another attempt by Microsoft to tighten up security for you.

Yes it was installed recently on that computer and the server, but I do not get the message on the server or any other computer running Explorer 7.

Zorak wrote:The warning that you are receiving is related to Internet Explorer 7. I think it has been installing recently through Windows Update. This is yet another attempt by Microsoft to tighten up security for you.

That explains it ... I haven't loaded Exploder 7.0 on any machines, either at home, or at church. I'm switching everyone to Firefox instead.

FWIW ... is there an option that you can set for this type of 'security check' ??

Googling that question will give you a variety of methods of side stepping this behavior. Due to the nature of these methods, though, actually lowering the "security" of the workstation, we officially don't recommend making any changes.

That still does not explain why I do not get this warning on the other computers running IE7. No one has has disabled any of the settings from defaults on these computers.

tborgal wrote:That still does not explain why I do not get this warning on the other computers running IE7. No one has has disabled any of the settings from defaults on these computers.

All said computers are running WinXP ?? Pro or home ??

I will need to check on two of the computers to be sure, but I know that the one I am using now is running Home with IE7 installed and I do not get that message. As soon as I find out about the other two I will post it.

Checked today and both the server - where PowerChurch is installed - and the laptop - which is giving me the warning - are XP Pro.

tborgal wrote:Checked today and both the server - where PowerChurch is installed - and the laptop - which is giving me the warning - are XP Pro.

Figures ... XP Pro is the business edition, and has added security features. It sounds like IE7 has added to those features with this helpful warning.

I suspect there is something at the Microsoft WinXP support site that will explain how to turn it off.

All of our networked computers run Win XP Pro. Three of them have updated to IE7. Only two display the security risk message when we try to run PowerChurch (ver 9). The one that doesn't display the warning is the one that acts as server for PowerChurch.
I'm wondering if there's something in the main PowerChurch directory that satisfies the security needs of IE7, that isn't on the client computers?

The difference is that it is a "local" program on that computer and therefore not a security risk, like running a program across the network would apparently is.

I thought there was a fix for this posted somewhere but I can not find it. Anyone have any idea where it might be, or what it was?