msi installs

[mirojr]

hi

 

Wondered if this was a coincidence or a design feature.

 

i tried assigning msi software in GPO

 

if i assigned it \\10.109.45.254\flowol\flowol.msi it didint install properly.

 

but if i used \\fileserver01\flowol\flowol.msi it worked fine

 

I dont know why.

 

Anyone?

 

ta

[sparkeh]

I seem to remember that assigning sofware via gpo requires the full UNC so that is expected behaviour.

[plexer]

I seem to remember that assigning sofware via gpo requires the full UNC so that is expected behaviour.

 

???

 

\\10.109.45.254\flowol\flowol.msi is a unc???

 

Ben

[plexer]

\\fileserver01\flowol\flowol.msi

 

Is not using the FQDN either.

 

Ben

[sparkeh]

???

 

\\10.109.45.254\flowol\flowol.msi is a unc???

 

Ben

 

Could be wrong but strictly speaking UNCs use hostnames ie \\servername\host not IP addresses.

 

Edit: This is from wikipedia but google any definition of UNC and you get

 

Uniform Naming Convention

The Microsoft Windows UNC, short for Universal Naming Convention or Uniform Naming Convention, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows systems has the generic form:

 

\\ComputerName\SharedFolder\Resource

Edited March 4, 2010 by sparkeh

[mirojr]

I agree.... but i think the goalposts have been changed.

 

2.2.1.4 UNC Path

 

Look at first bullet point.

[mirojr]

It needs a new name!!!

 

UNCIP

[sparkeh]

Cool

But I am pretty certain that for software via gpo you need to use the hostname.

[srochford]

Can't see any reason why you shouldn't be able to use the IP address! the GPSI process is going to take the UNC, look up the server name and then connect to the server by using that IP.

 

I wouldn't do it like that - makes life unnecessarily difficult when you want to move to new IPs (and I wouldn't use the server name either; I'd use DFS - much, much easier when you want to replace the server!)

 

What does it say in the event log? It should have logged a reason for the install fail.

[sparkeh]

Can't see any reason why you shouldn't be able to use the IP address

 

To be honest I kinda agree, just passing on that the MS documentation on this says to use the hostname.

Although do you have DNS reverse lookup working correctly? That could conceivable stop this working.

[mirojr]

To be honest I kinda agree, just passing on that the MS documentation on this says to use the hostname.

Although do you have DNS reverse lookup working correctly? That could conceivable stop this working.

 

I thought that. But it seems ok.

 

I wouldn't do it like that - makes life unnecessarily difficult when you want to move to new IPs (and I wouldn't use the server name either; I'd use DFS - much, much easier when you want to replace the server!)

 

How do i set up this DFS?

 

I really like the sound of this.

 

What route should i go down.

 

I have freenas and i was trying to sort something like this. I also have smb shares on linux box.

 

I just wonder about permissions

 

Thanks

[ajbritton]

It's just a thought, but it may be to do with Internet Explorer security settings that apply different rules to files being accessed via IP address.

 

The security settings in IE are based on different zones and I would guess that any IP address would be classed as the Internet Zone and as such, direct execution of files hosted on that address (installing an MSI would count as executing it) would be blocked.

 

I've seen this behaviour else, notably when doing mailmerges with data files on the network.

[powdarrmonkey]

It's just a thought, but it may be to do with Internet Explorer security settings that apply different rules to files being accessed via IP address.

 

The security settings in IE are based on different zones and I would guess that any IP address would be classed as the Internet Zone and as such, direct execution of files hosted on that address (installing an MSI would count as executing it) would be blocked.

 

I've seen this behaviour else, notably when doing mailmerges with data files on the network.

 

Precisely. Long ago in a moment of stupidity, Microsoft decided that the best way to decide if an address is in the local or remote (local intranet or internet) zones was to check if it has a full stop in it. Yes: internet; no: intranet. This is why fully-qualified but otherwise internal addresses get put in the internet zone and IE refuses to trust them.